[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fsgi2lax.fsf@collabora.com>
Date: Fri, 23 Sep 2022 10:54:30 -0400
From: Gabriel Krisman Bertazi <krisman@...labora.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: tytso@....edu, adilger.kernel@...ger.ca, jaegeuk@...nel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
kernel@...labora.com
Subject: Re: [PATCH v9 0/8] Clean up the case-insensitive lookup path
Eric Biggers <ebiggers@...nel.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
Powered by blists - more mailing lists