From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Cc: "darrick.wong@oracle.com" <darrick.wong@oracle.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"jth@kernel.org" <jth@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hare@suse.de" <hare@suse.de>,
Naohiro Aota <Naohiro.Aota@wdc.com>
Subject: Re: [PATCH v9 1/2] fs: New zonefs file system
Date: Wed, 29 Jan 2020 04:14:47 +0000 [thread overview]
Message-ID: <66069013676fc49042b3cf96d30d98963c57f79d.camel@wdc.com> (raw)
In-Reply-To: <1928f213-f6c8-156f-a968-6d0603a7656c@web.de>
On Tue, 2020-01-28 at 17:24 +0100, Markus Elfring wrote:
> …
> > +++ b/fs/zonefs/Kconfig
> …
> > + help
> > + zonefs is a simple File System which exposes zones of a zoned block
>
> Does the capitalisation matter here?
> Would the spelling “Zonefs is a simple file system which …” be appropriate?
Fixed. Thanks !
>
> Regards,
> Markus
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-01-29 4:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 16:24 [PATCH v9 1/2] fs: New zonefs file system Markus Elfring
2020-01-29 4:14 ` Damien Le Moal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-28 15:34 Markus Elfring
2020-01-29 4:13 ` Damien Le Moal
2020-01-27 12:49 Markus Elfring
2020-01-28 1:26 ` Damien Le Moal
2020-01-28 1:28 ` Linus Torvalds
2020-01-28 1:34 ` Damien Le Moal
2020-01-27 10:05 [PATCH v9 0/2] " Damien Le Moal
2020-01-27 10:05 ` [PATCH v9 1/2] fs: " Damien Le Moal
2020-01-28 17:46 ` Darrick J. Wong
2020-01-29 13:06 ` Damien Le Moal
2020-01-29 21:33 ` Dave Chinner
2020-01-30 3:00 ` Damien Le Moal
2020-01-30 22:59 ` Dave Chinner
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=66069013676fc49042b3cf96d30d98963c57f79d.camel@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=Markus.Elfring@web.de \
--cc=Naohiro.Aota@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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).