Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #89741 > unrolled thread

Bug#1118660: closing 1118660

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1118660: closing 1118660 Salvatore Bonaccorso <carnil@debian.org> - 2025-10-23 22:00 +0200
    Processed: closing 1118660 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-10-23 22:00 +0200
    Bug#1118660: closing 1118660 Guido Berhoerster <guido+debian@berhoerster.name> - 2025-10-24 07:00 +0200
      Bug#1118660: closing 1118660 Salvatore Bonaccorso <carnil@debian.org> - 2025-10-25 10:10 +0200
        Bug#1118660: closing 1118660 Salvatore Bonaccorso <carnil@debian.org> - 2025-10-25 10:40 +0200

#89741 — Bug#1118660: closing 1118660

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.

Once that has happend the fix will flow in one of the next 6.12.y stable series
updates.

Regards,
Salvatore

[toc] | [next] | [standalone]

#89742 — Processed: closing 1118660

Processing commands for control@bugs.debian.org:

> close 1118660 6.13~rc6-1~exp1
Bug #1118660 [src:linux] linux-image-6.12.48+deb13-amd64: Intel Wi-Fi 7 Bluetooth (BE20*) not working
Marked as fixed in versions linux/6.13~rc6-1~exp1.
Bug #1118660 [src:linux] linux-image-6.12.48+deb13-amd64: Intel Wi-Fi 7 Bluetooth (BE20*) not working
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1118660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118660
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#89750

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

On Thu, 23 Oct 2025 21:48:34 +0200 Salvatore Bonaccorso
<carnil@debian.org> 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

[toc] | [prev] | [next] | [standalone]

#89764

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
> <carnil@debian.org> 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

[toc] | [prev] | [next] | [standalone]

#89768

On Sat, Oct 25, 2025 at 10:02:27AM +0200, Salvatore Bonaccorso wrote:
> 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
> > <carnil@debian.org> 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.

Asked in
https://lore.kernel.org/stable/aPyGqPklZSrC7FJ2@eldamar.lan/T/#u .

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web