From: Daniel Rosenberg via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org,
Daniel Rosenberg <drosen@google.com>,
linux-doc@vger.kernel.org
Subject: [f2fs-dev] [PATCH v3 0/2] Casefolding in F2FS
Date: Thu, 18 Jul 2019 17:03:20 -0700 [thread overview]
Message-ID: <20190719000322.106163-1-drosen@google.com> (raw)
These patches are largely based on the casefolding patches for ext4
v3: Addressed feedback, apart from F2FS_CASEFOLD_FL/FS_CASEFOLD_FL
Added sysfs file "encoding" to see the encoding set on a filesystem
v2: Rebased patches again master, changed f2fs_msg to f2fs_info/f2fs_err
Daniel Rosenberg (2):
f2fs: include charset encoding information in the superblock
f2fs: Support case-insensitive file name lookups
fs/f2fs/dir.c | 126 ++++++++++++++++++++++++++++++++++++----
fs/f2fs/f2fs.h | 21 ++++++-
fs/f2fs/file.c | 9 +++
fs/f2fs/hash.c | 35 ++++++++++-
fs/f2fs/inline.c | 4 +-
fs/f2fs/inode.c | 4 +-
fs/f2fs/namei.c | 21 +++++++
fs/f2fs/super.c | 100 +++++++++++++++++++++++++++++++
fs/f2fs/sysfs.c | 23 ++++++++
include/linux/f2fs_fs.h | 9 ++-
10 files changed, 334 insertions(+), 18 deletions(-)
--
2.22.0.657.g960e92d24f-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-07-19 1:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 0:03 Daniel Rosenberg via Linux-f2fs-devel [this message]
2019-07-19 0:03 ` [f2fs-dev] [PATCH v3 1/2] f2fs: include charset encoding information in the superblock Daniel Rosenberg via Linux-f2fs-devel
2019-07-19 2:03 ` Chao Yu
2019-07-19 0:03 ` [f2fs-dev] [PATCH v3 2/2] f2fs: Support case-insensitive file name lookups Daniel Rosenberg via Linux-f2fs-devel
2019-07-19 2:11 ` Chao Yu
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=20190719000322.106163-1-drosen@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=corbet@lwn.net \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).