From: Chao Yu <yuchao0@huawei.com>
To: Junling Zheng <zhengjunling0206@163.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] mkfs.f2fs: use an array to manage features
Date: Mon, 16 Apr 2018 10:02:28 +0800 [thread overview]
Message-ID: <aa3f5007-4384-0410-080d-ed4137c486d7@huawei.com> (raw)
In-Reply-To: <1523802993-6179-1-git-send-email-zhengjunling0206@163.com>
On 2018/4/15 22:36, Junling Zheng wrote:
> From: Junling Zheng <zhengjunling@huawei.com>
>
> Use an array to manage features and their masks for mkfs.
>
> Signed-off-by: Junling Zheng <zhengjunling@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
parent reply other threads:[~2018-04-16 2:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1523802993-6179-1-git-send-email-zhengjunling0206@163.com>]
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=aa3f5007-4384-0410-080d-ed4137c486d7@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zhengjunling0206@163.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).