Bug#989705: closing 989705
Hi,
On Sun, Feb 05, 2023 at 06:20:54PM +0100, Computer Enthusiastic wrote:
> Hello Salvatore,
>
> On Tue, 4 Oct 2022 19:39:23 +0200 Computer Enthusiastic
> <computer.enthusiastic@gmail.com> 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].
> >
> > Thanks.
> >
> > [0] https://lists.freedesktop.org/archives/nouveau/2022-September/041182.html
>
> Thank you for supporting me to explain upstream the request for backporting
> the patch to 5.10.y.
>
> The patch has been backported to Linux 5.10.166 few days ago [1].
>
> I suppose it will hopefully be available in the Linux kernel shipped with
> the next Debian point release.
Yes I'm aware. It will be in the update which rebases to at least to
5.10.166 and is currently pending at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/644 .
Regards,
Salvatore
Reply to: