[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 22.12.22 13:36, Thorsten Leemhuis wrote:
> [Note: this mail contains only information for Linux kernel regression
> tracking. Mails like these contain '#forregzbot' in the subject to make
> then easy to spot and filter out. The author also tried to remove most
> or all individuals from the list of recipients to spare them the hassle.]
>
> On 21.12.22 02:10, Mikhail Gavrilov wrote:
>> Hi,
>> The kernel 6.2 preparation cycle has begun.
>> And after the kernel was updated on my laptop, the wifi stopped working.
>>
>> Bisecting blames this commit:
>> cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae is the first bad commit
>> commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae
>> Author: Lorenzo Bianconi <lorenzo@xxxxxxxxxx>
>> Date: Sat Nov 12 16:40:35 2022 +0100
>>
>> wifi: mt76: add WED RX support to mt76_dma_{add,get}_buf
>>
>
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
>
> #regzbot introduced cd372b8c99c5a5 ^
> https://bugzilla.kernel.org/show_bug.cgi?id=216829
> #regzbot title wifi: mt76: wifi stopped working
> #regzbot ignore-activity
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Regzbot for some reason missed to notice the fix properly, so point to
it manually:
#regzbot fix 953519b35227
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
