From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: ebiggers@kernel.org, andrealmeid@igalia.com,
qkrwngud825@gmail.com, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, zhanxusheng@xiaomi.com
Subject: Re: [RFC PATCH] f2fs: fold casefolded names of F2FS_NAME_LEN bytes
Date: Mon, 16 Nov 2026 20:21:46 +0800 [thread overview]
Message-ID: <20261116122146.2616475-1-zhanxusheng1024@gmail.com> (raw)
In-Reply-To: <20261103030712.1514800-1-zhanxusheng1024@gmail.com>
Hi Jaegeuk, Chao,
Gentle ping. The open question is the hash change: a new entry for
such a name is hashed by its folded form, so a kernel without this
patch cannot find it ("back on the current kernel" above). Is that
acceptable?
Thanks,
Zhan Xusheng
prev parent reply other threads:[~2026-11-16 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 3:07 Zhan Xusheng
2026-11-16 12:21 ` Zhan Xusheng [this message]
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=20261116122146.2616475-1-zhanxusheng1024@gmail.com \
--to=zhanxusheng1024@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=qkrwngud825@gmail.com \
--cc=zhanxusheng@xiaomi.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
all inboxes | Powered by JetHome®