From: Sheng Yong <shengyong1@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com
Cc: heyunlei@huawei.com, miaoxie@huawei.com, shengyong1@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [RFC PATCH 0/2] f2fs: introduce lost+found feature
Date: Tue, 6 Feb 2018 12:31:16 +0800 [thread overview]
Message-ID: <20180206043118.134137-1-shengyong1@huawei.com> (raw)
This patchset introduces lost+found feature in f2fs. If the feature is
enabled, f2fs should avoid to encrypting root directory.
For more information, please check the mail "f2fs-tools: introduce lost+
found feature".
Thanks,
Sheng
Sheng Yong (2):
f2fs: clean up f2fs_sb_has_xxx functions
f2fs: introduce lost+found feature
fs/f2fs/data.c | 2 +-
fs/f2fs/f2fs.h | 53 +++++++++++++++--------------------------------------
fs/f2fs/file.c | 6 +++---
fs/f2fs/segment.c | 4 ++--
fs/f2fs/super.c | 26 +++++++++++++++++++-------
fs/f2fs/sysfs.c | 4 ++--
6 files changed, 42 insertions(+), 53 deletions(-)
--
2.11.0
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-02-06 4:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 4:31 Sheng Yong [this message]
2018-02-06 4:31 ` [RFC PATCH 1/2] f2fs: clean up f2fs_sb_has_xxx functions Sheng Yong
2018-02-08 13:21 ` Chao Yu
2018-02-06 4:31 ` [RFC PATCH 2/2] f2fs: introduce lost+found feature Sheng Yong
2018-02-08 13:29 ` Chao Yu
2018-02-09 3:22 ` Sheng Yong
2018-02-10 2:50 ` [RFC PATCH 0/2] " Jaegeuk Kim
2018-02-11 1:53 ` Sheng Yong
2018-02-12 0:10 ` Jaegeuk Kim
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=20180206043118.134137-1-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=miaoxie@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).