From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Takashi Iwai <tiwai@suse.de>, Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-firmware@kernel.org, linux-kernel@vger.kernel.org,
Josh Boyer <jwboyer@kernel.org>
Subject: Re: [FIRMWARE] Regression on rtw89/rtw8852b_fw.bin by the latest update
Date: Sat, 18 Mar 2023 09:04:40 +0100 [thread overview]
Message-ID: <9a174e48-5cd6-535f-4f01-4e81398e772f@leemhuis.info> (raw)
In-Reply-To: <878rfuo67a.wl-tiwai@suse.de>
On 18.03.23 08:43, Takashi Iwai wrote:
>
> we've received a regression report on openSUSE Tumbleweed about the
> Realtek WiFi, and the culprit was spotted to be the latest firmware
> update of rtw89/rtw8852b_fw.bin. The former working linux-firmware
> tree was at the commit 5c11a3742947, while broken at 5bc279fb161d.
>
> The details are found in:
> https://bugzilla.opensuse.org/show_bug.cgi?id=1209449
>
> Could you check the problem?
> (Or feel free to join to the bugzilla entry above.)
FWIW, I already CCed Josh on the following bug yesterday in a comment
where I suggested the updated firmware should be reverted:
https://bugzilla.kernel.org/show_bug.cgi?id=217207
But it's likely a good idea to write a normal mail, so thx for that!
FWIW, the issue is also discussed here:
https://lore.kernel.org/all/df1ce994-3368-a57e-7078-8bdcccf4a1fd@gmail.com/#t
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
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-03-18 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 7:43 [FIRMWARE] Regression on rtw89/rtw8852b_fw.bin by the latest update Takashi Iwai
2023-03-18 8:04 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-18 14:05 ` Ping-Ke Shih
2023-03-18 15:34 ` Takashi Iwai
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=9a174e48-5cd6-535f-4f01-4e81398e772f@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.