On 24/03/12 11:54AM, Jens Axboe wrote: > On 3/12/24 9:21 AM, Jens Axboe wrote: > > On 3/12/24 9:14 AM, Fedor Pchelkin wrote: > >> On 24/03/12 08:34AM, Jens Axboe wrote: > >>> On 3/12/24 8:23 AM, Fedor Pchelkin wrote: > >> > >> [...] > >> > >>>> I feel io_uring-SCM related code should be dropped entirely from the > >>>> stable branches as the backports already differ greatly between versions > >>>> and some parts are still kept, some have been dropped in a non-consistent > >>>> order. Though this might contradict with stable kernel rules or be > >>>> inappropriate for some other reason. > >>> > >>> Looks fine to me, and I agree, it makes much more sense to drop it all > >>> from 5.10/5.15-stable as well to keep them in sync with upstream. And I > >>> think this is fine for stable, dropping code is always a good thing. > >>> > >> > >> Alright, got it. So that would require dropping it from all of the > >> supported 5.4, 6.1, 6.6, 6.7, too. > >> > >> Would it be okay if I'll send this as a series? > > > > Yeah I think so, keeping the code more in sync is always a good thing > > when it comes to stable. Just make sure you mark the backport commits > > with the appropriate upstream shas. Thanks! > > I'll just do these backports myself, thanks for bringing it up. Great, thanks! -- Fedor
