----- Original Message -----
> From: "Salvatore Bonaccorso" <car...@debian.org>
> To: "Timothy Pearson" <tpear...@raptorengineering.com>, "990279"
> <990...@bugs.debian.org>
> Cc: "Christian König" <christian.koe...@amd.com>, "Xi Ruoyao"
> <xry...@mengyan1223.wang>, "Alex Deucher"
> <alexander.deuc...@amd.com>
> 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" <christian.koe...@amd.com>
>> > To: "Timothy Pearson" <tpear...@raptorengineering.com>, "Salvatore
>> > Bonaccorso"
>> > <car...@debian.org>
>> >>
>> >> 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/20220209201624.1234062-1-car...@debian.org/T/#u
>
> Regards,
> Salvatore
Understood, apologies for the mixup. I'll monitor the upstream submission and
help push it through if needed.
Thanks!
