From: Kalle Valo <kvalo@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: "Greenman, Gregory" <gregory.greenman@intel.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Peer, Ilan" <ilan.peer@intel.com>,
"anarcat@debian.org" <anarcat@debian.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: Microcode SW error since Linux 6.5
Date: Wed, 04 Oct 2023 16:12:03 +0300 [thread overview]
Message-ID: <87h6n6h6qk.fsf@kernel.org> (raw)
In-Reply-To: <0c07b6bf-a9cc-4dc0-b71c-a2257e501e5f@leemhuis.info> (Linux regression tracking's message of "Wed, 4 Oct 2023 10:35:54 +0200")
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:
>> The patch in [1] should solve the issue. The problem was that wrong version
>> of Firmware API was used for some older versions.
>>
>> [1]
>> https://patchwork.kernel.org/project/linux-wireless/patch/20230926165546.086e635fbbe6.Ia660f35ca0b1079f2c2ea92fd8d14d8101a89d03@changeid/
>
> Ahh, great, many thx for the reply. Two things then:
>
> (1) I wanted to ask why this patch is not in mainline or -net yet, but
> then noticed the fix is among the patches of a one week old pull request
> that afaics was not handled yet:
> https://lore.kernel.org/all/20230927095835.25803-2-johannes@sipsolutions.net/
>
> Guess that one fell through the cracks due to the Netconf 2023 workshop?
> Maybe this msg gets things rolling again.
At least on Monday there were something 500 patches in netdev patchwork
and today I see still 340 patches. Understandably it takes time to
process all that, let's just wait patiently and let the maintainers do
their job in peace.
I see our pull request is in active state in patchwork so I don't think
it has fell through the cracks:
https://patchwork.kernel.org/project/netdevbpf/patch/20230927095835.25803-2-johannes@sipsolutions.net/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-04 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 17:24 Microcode SW error since Linux 6.5 Antoine Beaupré
2023-09-21 19:10 ` Greenman, Gregory
2023-09-21 19:29 ` Johannes Berg
2023-09-25 2:43 ` Antoine Beaupré
2023-09-25 6:03 ` Johannes Berg
2023-09-25 18:39 ` Antoine Beaupré
2023-09-25 19:03 ` Johannes Berg
2023-10-03 11:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 7:51 ` Greenman, Gregory
2023-10-04 8:35 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-04 13:12 ` Kalle Valo [this message]
2023-10-04 15:34 ` Johannes Berg
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=87h6n6h6qk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=anarcat@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregory.greenman@intel.com \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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