linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: dhowells@redhat.com, Alexander Viro <viro@zeniv.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	devel@driverdev.osuosl.org, linux-erofs@lists.ozlabs.org,
	Chao Yu <yuchao0@huawei.com>, Miao Xie <miaoxie@huawei.com>,
	weidu.du@huawei.com
Subject: Re: [PATCH 1/2 dhowells/mount-api] staging: erofs: rename superblock flags (MS_xyz -> SB_xyz)
Date: Thu, 06 Sep 2018 11:08:09 +0100	[thread overview]
Message-ID: <17402.1536228489@warthog.procyon.org.uk> (raw)
In-Reply-To: <1536224508-66168-1-git-send-email-gaoxiang25@huawei.com>

Gao Xiang <gaoxiang25@huawei.com> wrote:

> This patch follows commit 1751e8a6cb93 ("Rename superblock
> flags (MS_xyz -> SB_xyz)") and after commit ("vfs: Suppress
> MS_* flag defs within the kernel unless explicitly enabled"),
> there is no MS_RDONLY and MS_NOATIME at all.
> 
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>

I recommend pushing this one to Linus now.  It's trivial enough.

Reviewed-by: David Howells <dhowells@redhat.com>

  parent reply	other threads:[~2018-09-06 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  9:01 [PATCH 1/2 dhowells/mount-api] staging: erofs: rename superblock flags (MS_xyz -> SB_xyz) Gao Xiang
2018-09-06  9:01 ` [PATCH 2/2 dhowells/mount-api] staging: erofs: update .mount and .remount_sb Gao Xiang
2018-09-06  9:39   ` Chao Yu
2018-09-06 10:08 ` David Howells [this message]
2018-09-06 10:37   ` [PATCH 1/2 dhowells/mount-api] staging: erofs: rename superblock flags (MS_xyz -> SB_xyz) Gao Xiang
2018-09-10  8:13     ` Greg Kroah-Hartman
2018-09-10  8:21       ` Gao Xiang
2018-09-06 10:09 ` [PATCH 2/2 dhowells/mount-api] staging: erofs: update .mount and .remount_sb David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17402.1536228489@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gaoxiang25@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=weidu.du@huawei.com \
    --cc=yuchao0@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).