Bug#989705: closing 989705

[Salvatore Bonaccorso <carnil@debian.org>]

Hi,

On Tue, Oct 04, 2022 at 07:39:23PM +0200, Computer Enthusiastic wrote:
> Hello Salvatore,
> 
> Il giorno mar 20 set 2022 alle ore 12:32 Salvatore Bonaccorso
> <carnil@debian.org> ha scritto:
> >
> > Hi,
> [..]
> > >
> > > What could be done to make the patch land in the current Debian Stable
> > > (Bullseye) kernel release ?
> >
> > It should land in the 5.10.y stable series which we will then pick up
> > automatically on next rebases. But what is puzzling is that the commit
> > has been marked for stable only v5.15+. If you were able to confirm it
> > is actually present in 5.10.y as well then it needs a followup to be
> > picked as well for the 5.10.y stable series.
> >
> > Regards,
> > Salvatore
> 
> Yes, the patch is marked as only v5.15+, but the issue is still there
> in kernel 5.10, too.
> 
> As you suggested, I have tested the vanilla kernel 5.10.145 with and
> without kernel patches, as reported here [0].

Seen that, and thanks for having taken the time to test the case with
and without patch with newest 5.10.y version. This will hopefully help
to get the patch applied to 5.10.y as well so we can pick it up.

Regards,
Salvatore