From: Chao Yu <chao@kernel.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>,
tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org,
ebiggers@kernel.org
Cc: linux-ext4@vger.kernel.org, kernel@collabora.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5 2/8] f2fs: Simplify the handling of cached insensitive names
Date: Thu, 19 May 2022 19:27:39 +0800 [thread overview]
Message-ID: <fb8aaa09-7bfd-7e2a-4cb1-de691fdb6408@kernel.org> (raw)
In-Reply-To: <20220518172320.333617-3-krisman@collabora.com>
On 2022/5/19 1:23, Gabriel Krisman Bertazi wrote:
> Keeping it as qstr avoids the unnecessary conversion in f2fs_match
>
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2022-05-19 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:23 [PATCH v5 0/8] Clean up the case-insensitive lookup path Gabriel Krisman Bertazi
2022-05-18 17:23 ` [PATCH v5 1/8] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi
2022-05-18 18:49 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 2/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 18:54 ` Eric Biggers
2022-05-19 11:27 ` Chao Yu [this message]
2022-05-19 11:32 ` [f2fs-dev] " Chao Yu
2022-05-18 17:23 ` [PATCH v5 3/8] libfs: Introduce case-insensitive string comparison helper Gabriel Krisman Bertazi
2022-05-18 19:05 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 4/8] ext4: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi
2022-05-18 19:20 ` Eric Biggers
2022-05-18 22:44 ` Gabriel Krisman Bertazi
2022-05-18 17:23 ` [PATCH v5 5/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 19:22 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 6/8] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-05-18 19:23 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 7/8] ext4: Move CONFIG_UNICODE defguards into the code flow Gabriel Krisman Bertazi
2022-05-18 19:25 ` Eric Biggers
2022-05-18 17:23 ` [PATCH v5 8/8] f2fs: " Gabriel Krisman Bertazi
2022-05-18 19:26 ` Eric Biggers
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=fb8aaa09-7bfd-7e2a-4cb1-de691fdb6408@kernel.org \
--to=chao@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=tytso@mit.edu \
/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).