The patch appears to be applied as of kernel security update 5.10.0-12, linux_5.10.103-1 source.

On Wed, 9 Feb 2022 14:22:23 -0600 (CST) Timothy Pearson <[email protected]> wrote:
>
>
> ----- Original Message -----
> > From: "Salvatore Bonaccorso" <[email protected]>
> > To: "Timothy Pearson" <[email protected]>, "990279" <[email protected]> > > Cc: "Christian König" <[email protected]>, "Xi Ruoyao" <[email protected]>, "Alex Deucher"
> > <[email protected]>
> > Sent: Wednesday, February 9, 2022 2:18:34 PM
> > Subject: Re: Bug#990279: Status?
>
> > Hi Timothy,
> >
> > On Wed, Feb 09, 2022 at 01:20:40PM -0600, Timothy Pearson wrote:
> >> ----- Original Message -----
> >> > From: "Christian König" <[email protected]>
> >> > To: "Timothy Pearson" <[email protected]>, "Salvatore Bonaccorso"
> >> > <[email protected]>
> >> >>
> >> >> If you need me to generate / submit a patch just let me know.
> >> >
> >> > Please do, I don't have time nor a test system to look into this.
> >> >
> >> > Regards,
> >> > Christian.
> >>
> >> Submitted here:
> >> <https://lists.debian.org/debian-kernel/2022/02/msg00099.html>
> >
> > This is not exactly what we meant. The idea is to submit it to
> > upstream for stable 5.10.y so we can pick it up in Debian. I'm taking
> > the backport in #47 now.
> >
> > It is now submitted here:
> > <https://lore.kernel.org/stable/[email protected]/T/#u>
> >
> > Regards,
> > Salvatore
>
> Understood, apologies for the mixup. I'll monitor the upstream submission and help push it through if needed.
>
> Thanks!
>
>



Reply via email to