From: Felix Fietkau <nbd@nbd.name>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
lorenzo@kernel.org, sujuan.chen@mediatek.com,
Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
spasswolf@web.de
Subject: Re: [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e
Date: Tue, 10 Jan 2023 09:00:11 +0100 [thread overview]
Message-ID: <BD7074C5-20BE-4D70-824B-0994892C995D@nbd.name> (raw)
In-Reply-To: <252b1fe4-ccc2-4ea8-1da5-9a60f7378fd6@leemhuis.info>
> On 10. Jan 2023, at 08:17, Linux kernel regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> [CCing spasswolf@web.de]
>
>> On 09.01.23 08:32, Linux kernel regression tracking (Thorsten Leemhuis)
>> wrote:
>>> On 04.01.23 15:20, Thorsten Leemhuis wrote:
>>> Hi, this is your Linux kernel regression tracker. Top-posting for once,
>>> to make this easily accessible to everyone.
>>>
>>> Felix, Lorenzo, did below fix for the regression
>>
>> There is another report about an issue with mediatek wifi in 6.2-rc:
>> https://bugzilla.kernel.org/show_bug.cgi?id=216901
>
> FWIW, "spasswolf" in that ticket posted a patch that according to the
> reporter of that bug fixes the issue:
> https://bugzilla.kernel.org/show_bug.cgi?id=216901#c5
>
> I only took a brief look, but it seems it does a subset of what Felix
> patch does.
>
>> To me this looks like a duplicate of the report that started this thread.
>>
>> (side note: there was another, earlier report that might be a dupe, too:
>> https://bugzilla.kernel.org/show_bug.cgi?id=216829 )>
>>> Mikhail reported make
>>> any progress to get mainlined? It doesn't look like it from here, but I
>>> suspect I missed something, that's why I'm asking.
>>
>> No reply. :-((
>
> Still no reply. I wonder if I'm holding things wrong. But well, let's
> wait one more day before escalating this further.
Johannes told me on IRC that he will review my patch soon. He simply has too many things to do at the moment.
- Felix
next prev parent reply other threads:[~2023-01-10 8:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 1:10 [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e Mikhail Gavrilov
2022-12-21 10:45 ` Felix Fietkau
2022-12-21 11:26 ` Lorenzo Bianconi
2022-12-21 13:10 ` Mikhail Gavrilov
2022-12-21 14:12 ` Felix Fietkau
2022-12-21 16:07 ` Lorenzo Bianconi
2022-12-21 16:46 ` Mikhail Gavrilov
2022-12-21 17:17 ` Felix Fietkau
2022-12-22 6:47 ` Mikhail Gavrilov
2022-12-24 7:55 ` Thorsten Leemhuis
2022-12-26 10:59 ` Thorsten Leemhuis
2023-01-04 14:20 ` Thorsten Leemhuis
2023-01-09 7:32 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 7:16 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 8:00 ` Felix Fietkau [this message]
2023-01-10 8:41 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 14:11 ` Kalle Valo
2023-01-10 21:52 ` Mikhail Gavrilov
2022-12-22 12:36 ` [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e #forregzbot Thorsten Leemhuis
2023-01-27 11:36 ` Linux kernel regression tracking (#update)
2023-01-17 0:33 [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e Mike Lothian
2023-01-17 5:42 ` Mikhail Gavrilov
2023-01-17 6:42 ` Kalle Valo
2023-01-17 13:06 ` Mike Lothian
2023-01-17 13:13 ` Mikhail Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD7074C5-20BE-4D70-824B-0994892C995D@nbd.name \
--to=nbd@nbd.name \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=spasswolf@web.de \
--cc=sujuan.chen@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).