On Wed, Jan 12, 2022 at 01:50:12PM +0100, Alexander Egorenkov wrote: > Hi Greg, > > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > > > On Wed, Jan 12, 2022 at 10:06:14AM +0100, Alexander Egorenkov wrote: > >> Hi Greg, > >> > >> <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > >> > >> > The patch below does not apply to the 5.15-stable tree. > >> > If someone wants it applied there, or to any other stable or longterm > >> > tree, then please email the backport, including the original git commit > >> > id to <stable@xxxxxxxxxxxxxxx>. > >> > > >> > thanks, > >> > > >> > greg k-h > >> > > >> > >> please apply the following upstream commits (in this order): > >> > >> 1. edce10ee21f3916f5da34e55bbc03103c604ba70 > > > > This commit fails to apply. > > > >> 2. 41967a37b8eedfee15b81406a9f3015be90d3980 > >> 3. abf0e8e4ef25478a4390115e6a953d589d1f9ffd (the failed commit) > > > > Can you please send a working set of backported patches that we can > > apply? > > > > I tested the stable branch 5.15.y and discovered that > the fix 41967a37b8eedfee15b81406a9f3015be90d3980 is already present > there. > > Please try to apply just abf0e8e4ef25478a4390115e6a953d589d1f9ffd again. > I think you probably tried to apply > abf0e8e4ef25478a4390115e6a953d589d1f9ffd before > 41967a37b8eedfee15b81406a9f3015be90d3980 was present ? > And now that is there, everything works. Ah, yes, I think that is what must have happened here, it now worked, thanks. greg k-h
