From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
linux-f2fs-devel@lists.sourceforge.net, adilger.kernel@dilger.ca,
jaegeuk@kernel.org, kernel@collabora.com
Subject: Re: [f2fs-dev] [PATCH v9 0/8] Clean up the case-insensitive lookup path
Date: Fri, 23 Sep 2022 10:54:30 -0400 [thread overview]
Message-ID: <87fsgi2lax.fsf@collabora.com> (raw)
In-Reply-To: <Yy0t8WYhM+Dv3gX1@sol.localdomain> (Eric Biggers's message of "Thu, 22 Sep 2022 20:54:25 -0700")
Eric Biggers <ebiggers@kernel.org> writes:
> On Tue, Sep 13, 2022 at 07:41:42PM -0400, Gabriel Krisman Bertazi wrote:
>> Hi,
>>
>> I'm resubmitting this as v9 since I think it has fallen through the
>> cracks :). It is a collection of trivial fixes for casefold support on
>> ext4/f2fs. More details below.
>>
>> It has been sitting on the list for a while and most of it is r-b
>> already. I'm keeping the tags for this submission, since there is no
>> modifications from previous submissions, apart from a minor conflict
>> resolution when merging to linus/master.
>
> Who are you expecting to apply this?
Hi Eric,
There are three groups of changes here: libfs, ext4 and f2fs. Since the
changes in libfs are self-contained and only affect these two
filesystems, I think it should be fine for them to go through a fs tree.
The bulk of changes are ext4, and Ted mentioned on an earlier version
that he could pick the first patches of this series, so I'm thinking it
should all go through the ext4 tree. If Jaegeuk acks, the f2fs changes
are safe to go with the rest, or I can send them afterwards as a
separate series once the libfs code is merged.
Thanks,
--
Gabriel Krisman Bertazi
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-09-23 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 23:41 [f2fs-dev] [PATCH v9 0/8] Clean up the case-insensitive lookup path Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 1/8] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 2/8] f2fs: " Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 3/8] libfs: Introduce case-insensitive string comparison helper Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 4/8] ext4: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi
2022-09-23 3:48 ` Eric Biggers
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 5/8] f2fs: " Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 6/8] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 7/8] ext4: Move CONFIG_UNICODE defguards into the code flow Gabriel Krisman Bertazi
2022-09-13 23:41 ` [f2fs-dev] [PATCH v9 8/8] f2fs: " Gabriel Krisman Bertazi
2022-09-23 3:54 ` [f2fs-dev] [PATCH v9 0/8] Clean up the case-insensitive lookup path Eric Biggers
2022-09-23 14:54 ` Gabriel Krisman Bertazi [this message]
2022-10-13 23:45 ` Gabriel Krisman Bertazi
2022-12-08 14:38 ` Muhammad Usama Anjum
2022-12-09 13:47 ` Gabriel Krisman Bertazi
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=87fsgi2lax.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=adilger.kernel@dilger.ca \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kernel@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).