linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: computersforpeace@gmail.com, linux-mtd@lists.infradead.org,
	hujianyang@huawei.com
Subject: Re: [PATCH v5] ubifs: respect MS_SILENT mount flag
Date: Mon, 02 Jun 2014 10:59:14 +0300	[thread overview]
Message-ID: <1401695954.11182.112.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20140531000054.GA12737@earthship.lan>

Thanks Daniel, this looks nicer than the original patch. Would you
please do few more cosmetic changes, though.

On Sat, 2014-05-31 at 02:01 +0200, Daniel Golle wrote: 
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index a81c7b5..e88bbb6 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -1149,6 +1149,8 @@ static int mount_ubifs(struct ubifs_info *c)
>  	size_t sz;
>  
>  	c->ro_mount = !!(c->vfs_sb->s_flags & MS_RDONLY);
> +	c->probing = !!(c->vfs_sb->s_flags & MS_SILENT);

Would you add a comment on top of this saying what MS_SILENT is about.
The kernel people who read the code do not necessary know the "FS
probing" use-case. E.g., I did not know about it.
> @@ -1441,6 +1451,7 @@ struct ubifs_info {
>  	unsigned int replaying:1;
>  	unsigned int mounting:1;
>  	unsigned int remounting_rw:1;
> +	unsigned int probing:1;

We have kerneldoc-style comment on top of this structure, could you
please document the new field there.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2014-06-02  7:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17  1:55 [PATCH] ubifs: respect MS_SILENT mount flag Daniel Golle
2014-05-27 12:18 ` Artem Bityutskiy
2014-05-27 14:11   ` [PATCH v2] " Daniel Golle
2014-05-27 14:56     ` Artem Bityutskiy
2014-05-27 16:04       ` Daniel
2014-05-28  2:11         ` hujianyang
2014-05-28  8:01           ` Artem Bityutskiy
2014-05-28  8:07             ` Bityutskiy, Artem
2014-05-28  8:14               ` Artem Bityutskiy
2014-05-28  8:28                 ` Artem Bityutskiy
2014-05-28  8:42                   ` hujianyang
2014-05-28  9:29                     ` Artem Bityutskiy
2014-05-30 22:01                 ` [PATCH v3] " Daniel Golle
2014-05-30 23:20                   ` Brian Norris
2014-05-30 23:32                     ` [PATCH v4] " Daniel Golle
2014-05-31  0:01                     ` [PATCH v5] " Daniel Golle
2014-06-02  7:59                       ` Artem Bityutskiy [this message]
2014-06-02 13:51                         ` [PATCH v6] " Daniel Golle
2014-06-02 15:01                           ` Artem Bityutskiy

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=1401695954.11182.112.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=daniel@makrotopia.org \
    --cc=hujianyang@huawei.com \
    --cc=linux-mtd@lists.infradead.org \
    /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).