Hi Guido, On Fri, Oct 24, 2025 at 06:48:03AM +0200, Guido Berhoerster wrote: > Hi Salvatore, > > On Thu, 23 Oct 2025 21:48:34 +0200 Salvatore Bonaccorso > <[email protected]> wrote: > > close 1118660 6.13~rc6-1~exp1 > > thanks > > > > Hi, > > > > Fixed in 6.13-rc1 upstream so upating the metadata. > > > > At first glance commit d88a8bb8bbbe ("Bluetooth: btintel: Add DSBR support > > for > > BlazarIW, BlazarU and GaP") does not look like a candidate accepted by > > upstream > > for stable series, but might be worth a try. > > that is the reason I kindly ask to include the attached (rebased) patch > in the trixie kernel package. It's already upstream, it fixes hardware > which will be very common during the trixie lifecycle and the backported > has already been tested and deployed by other distros such as Ubuntu or > SUSE*. > > Once that has happend the fix will flow in one of the next 6.12.y stable > > series > > updates. > Thanks,-- Guido Berhoerster* > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2085538 > > https://code.opensuse.org/kernel/kernel-source/c/a37dcc1c6f5bf37cc957662de69eb7d2c519c31a?branch=8f4705b70a5b7c733278b56ea318bde7a101e7e1
Ubuntu and SUSE have different strategies, we follow the stable series and want to keep delta as close as possible. What i will do is asking stable list if they can consider picking the commit for 6.12.y which will help you. Otherwise given it touches drivers/bluetooth/btintel.c for non-isolated code I would rather suggest to use the backports kernel in this case. I will add you in the loop for the backports request, and then we see which road to go. Regards, Salvatore
