From: Randy Dunlap <rdunlap@infradead.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Johannes Thumshirn <jth@kernel.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v13 2/2] zonefs: Add documentation
Date: Wed, 19 Feb 2020 17:15:44 -0800 [thread overview]
Message-ID: <6f370a74-877a-a709-e7ff-ba7dc1963ece@infradead.org> (raw)
In-Reply-To: <BYAPR04MB58167DDA2AE7B1BC1500D9C4E7130@BYAPR04MB5816.namprd04.prod.outlook.com>
On 2/19/20 4:59 PM, Damien Le Moal wrote:
> On 2020/02/20 9:55, Randy Dunlap wrote:
>> Hi Damien,
>>
>> Typo etc. corrections below:
>
> Thanks. Will correct these. Since this is now in the kernel, you can send a
> patch too :)
oops, sorry, I didn't notice that.
I'll be glad to send a patch.
>
>>
>> On 2/6/20 7:16 PM, Damien Le Moal wrote:
>>> Add the new file Documentation/filesystems/zonefs.txt to document
>>> zonefs principles and user-space tool usage.
>>>
>>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
>>> Reviewed-by: Dave Chinner <dchinner@redhat.com>
>>> ---
>>> Documentation/filesystems/zonefs.txt | 404 +++++++++++++++++++++++++++
>>> MAINTAINERS | 1 +
>>> 2 files changed, 405 insertions(+)
>>> create mode 100644 Documentation/filesystems/zonefs.txt
--
~Randy
prev parent reply other threads:[~2020-02-20 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 3:16 [PATCH v13 0/2] New zonefs file system Damien Le Moal
2020-02-07 3:16 ` [PATCH v13 1/2] fs: " Damien Le Moal
2020-02-07 4:06 ` Dave Chinner
2020-02-07 3:16 ` [PATCH v13 2/2] zonefs: Add documentation Damien Le Moal
2020-02-20 0:55 ` Randy Dunlap
2020-02-20 0:59 ` Damien Le Moal
2020-02-20 1:15 ` Randy Dunlap [this message]
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=6f370a74-877a-a709-e7ff-ba7dc1963ece@infradead.org \
--to=rdunlap@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.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 \
/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).