Re: three commits you might or might not want to pick up for 6.9.y

From: Greg KH
Date: Fri May 17 2024 - 06:37:35 EST


On Wed, May 15, 2024 at 04:09:17PM +0200, Greg KH wrote:
> On Wed, May 15, 2024 at 03:49:30PM +0200, Thorsten Leemhuis wrote:
> > 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@xxxxxxxxxxxxxx/
> >
> > 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@xxxxxxxxxxxxxx/
> >
> >
> > * leds/iwlwifi: hangs on boot:
> > https://lore.kernel.org/lkml/30f757e3-73c5-5473-c1f8-328bab98fd7d@xxxxxxxxxxxxxxx/
> >
> > 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.
>
> Nice, thanks for these! I'll look at them after this round of -rcs is
> out.

All now queued up.

greg k-h