On Thu, Sep 1, 2022 at 12:41 PM Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Thu, Sep 01, 2022 at 12:30:13PM +0300, Amir Goldstein wrote: > > On Thu, Sep 1, 2022 at 12:04 PM Frank Hofmann <fhofmann@xxxxxxxxxxxxxx> wrote: > > > > > > On Thu, Sep 1, 2022 at 6:49 AM Amir Goldstein <amir73il@xxxxxxxxx> wrote: > > > > > > > > From: Dave Chinner <dchinner@xxxxxxxxxx> > > > > > > > > commit 9a5280b312e2e7898b6397b2ca3cfd03f67d7be1 upstream. > > > > > > > > [backport for 5.10.y] > > > > > > Hi Amir, hi Dave, > > > > > > I've got no objections to backporting this change at all. We've been > > > using the patch on our internal 5.15 tracker branch happily for > > > several months now. > > > > > > Would like to highlight though that it's currently not yet merged in > > > linux-stable 5.15 branch either (it's in 5.19 and mainline alright). > > > If this gets queued for 5.10 then maybe it also should be for 5.15 ? > > > > > > > Hi Frank, > > > > Quoting from my cover letter: > > > > Patches 6-7 in this 5.10.y update have not been applied to 5.15.y yet. > > I pointed Leah's attention to these patches and she said she will > > include them in a following 5.15.y update. > > And as you know, this means I can't take this series at all until that > series is ready, so to help us out, in the future, just don't even send > them until they are all ready together. > What? You cannot take backports to 5.10.y before they are applied to 5.15.y? Since when? Thanks, Amir.
