Message ID | 20220913234150.513075-1-krisman@collabora.com |
---|---|
Headers | show |
Series | Clean up the case-insensitive lookup path | expand |
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? - Eric
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 <krisman@collabora.com> writes: > 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. Ted, Does the above plan work for you? Do you intend to pick this up for the next merge window?
On 10/14/22 4:45 AM, Gabriel Krisman Bertazi wrote: > Gabriel Krisman Bertazi <krisman@collabora.com> writes: > >> 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. > > Ted, > > Does the above plan work for you? Do you intend to pick this up for the > next merge window? It seems like this series hasn't been picked up. Any ideas on what can be done?
Muhammad Usama Anjum <usama.anjum@collabora.com> writes: > On 10/14/22 4:45 AM, Gabriel Krisman Bertazi wrote: >> Gabriel Krisman Bertazi <krisman@collabora.com> writes: >> >>> 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. >> >> Ted, >> >> Does the above plan work for you? Do you intend to pick this up for the >> next merge window? > It seems like this series hasn't been picked up. Any ideas on what can > be done? I got tired of the radio silence and gave up on it. If there is interest, feel free to respin it once more.