From: Daniel Rosenberg <drosen@google.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-f2fs-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, kernel-team@android.com,
Daniel Rosenberg <drosen@google.com>
Subject: [PATCH v2 0/2] Casefolding in F2FS
Date: Tue, 16 Jul 2019 20:14:06 -0700 [thread overview]
Message-ID: <20190717031408.114104-1-drosen@google.com> (raw)
These patches are largely based on the casefolding patches for ext4
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 | 133 ++++++++++++++++++++++++++++++++++++----
fs/f2fs/f2fs.h | 24 ++++++--
fs/f2fs/file.c | 10 ++-
fs/f2fs/hash.c | 34 +++++++++-
fs/f2fs/inline.c | 6 +-
fs/f2fs/inode.c | 4 +-
fs/f2fs/namei.c | 21 +++++++
fs/f2fs/super.c | 86 ++++++++++++++++++++++++++
include/linux/f2fs_fs.h | 9 ++-
9 files changed, 303 insertions(+), 24 deletions(-)
--
2.22.0.510.g264f2c817a-goog
next reply other threads:[~2019-07-17 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 3:14 Daniel Rosenberg [this message]
2019-07-17 3:14 ` [PATCH v2 1/2] f2fs: include charset encoding information in the superblock Daniel Rosenberg
2019-07-17 9:39 ` Chao Yu
2019-07-17 3:14 ` [PATCH v2 2/2] f2fs: Support case-insensitive file name lookups Daniel Rosenberg
2019-07-17 10:11 ` Chao Yu
2019-07-18 21:31 ` Daniel Rosenberg
2019-07-19 2:01 ` 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=20190717031408.114104-1-drosen@google.com \
--to=drosen@google.com \
--cc=corbet@lwn.net \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).