From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>
Subject: three commits you might or might not want to pick up for 6.9.y
Date: Wed, 15 May 2024 15:49:30 +0200 [thread overview]
Message-ID: <9e40badb-c4fa-4828-a4c5-3a170f624215@leemhuis.info> (raw)
Hi Greg. Here are three reports for regressions introduced during the
6.9 cycle that were not fixed for 6.9 for one reason or another, but are
fixed in mainline now. So they might be good candidates to pick up early
for 6.9.y -- or maybe not, not sure. You are the better judge here. I
just thought you might wanted to know about them.
* net: Bluetooth: firmware loading problems with older firmware:
https://lore.kernel.org/lkml/20240401144424.1714-1-mike@fireburn.co.uk/
Fixed by 958cd6beab693f ("Bluetooth: btusb: Fix the patch for MT7920 the
affected to MT7921") – which likely should have gone into 6.9, but did
not due to lack of fixes: an stable tags:
https://lore.kernel.org/all/CABBYNZK1QWNHpmXUyne1Vmqqvy7csmivL7q7N2Mu=2fmrUV4jg@mail.gmail.com/
* leds/iwlwifi: hangs on boot:
https://lore.kernel.org/lkml/30f757e3-73c5-5473-c1f8-328bab98fd7d@candelatech.com/
Fixed by 3d913719df14c2 ("wifi: iwlwifi: Use request_module_nowait") –
not sure if that one is worth it, the regression might be an exotic
corner case.
* Ryzen 7840HS CPU single core never boosts to max frequency:
https://bugzilla.kernel.org/show_bug.cgi?id=218759
Fixed by bf202e654bfa57 ("cpufreq: amd-pstate: fix the highest frequency
issue which limits performance") – which was broken out of a patch-set
by the developers to send it in for 6.9, but then was only merged for
6.10 by the maintainer.
Ciao, Thorsten
next reply other threads:[~2024-05-15 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 13:49 Thorsten Leemhuis [this message]
2024-05-15 14:09 ` three commits you might or might not want to pick up for 6.9.y Greg KH
2024-05-17 10:37 ` Greg KH
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=9e40badb-c4fa-4828-a4c5-3a170f624215@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).