quot; , "990279"
<990...@bugs.debian.org>
> > Cc: "Christian König" , "Xi Ruoyao"
, "Alex Deucher"
> >
> > Sent: Wednesday, February 9, 2022 2:18:34 PM
> > Subject: Re: Bug#990279: Status?
>
> > Hi Timothy,
> >
- Original Message -
> From: "Salvatore Bonaccorso"
> To: "Timothy Pearson" , "990279"
> <990...@bugs.debian.org>
> Cc: "Christian König" , "Xi Ruoyao"
> , "Alex Deucher"
>
> Sent: Wednesday, Fe
Hi Timothy,
On Wed, Feb 09, 2022 at 01:20:40PM -0600, Timothy Pearson wrote:
> - Original Message -
> > From: "Christian König"
> > To: "Timothy Pearson" , "Salvatore
> > Bonaccorso"
> >>
> >> If you need me to generate / submit a patch just let me know.
> >
> > Please do, I don't
- Original Message -
> From: "Salvatore Bonaccorso"
> To: "Timothy Pearson" , "990279"
> <990...@bugs.debian.org>
> Cc: "Christian König" , "Xi Ruoyao"
> , "Alex Deucher"
>
> Sent: Tuesday, Fe
Hi Timothy,
On Tue, Feb 08, 2022 at 01:23:10PM -0600, Timothy Pearson wrote:
> I can confirm Bullseye is still affected by this bug.
>
> Is there any chance of this fix being applied to the Bullseye stable
> kernels? We're having to maintain kernel builds in our own
> repositories to fix this
I can confirm Bullseye is still affected by this bug.
Is there any chance of this fix being applied to the Bullseye stable kernels?
We're having to maintain kernel builds in our own repositories to fix this
regression, and that introduces some lag when e.g. security updates are pushed
to
6 matches
Mail list logo
