Linux bluetooth development
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Christoph Zwerschke <cito@online.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Erik Brangs <erik.brangs@gmx.de>,
	benh@debian.org, stable@vger.kernel.org,
	regressions@lists.linux.dev, linux-bluetooth@vger.kernel.org,
	1149377@bugs.debian.org,
	Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [regression 6.12.y] After backport of 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") bluethooth not anymore working on 0b05:1bef ASUSTek Computer, Inc. Bluetooth Controller (requests firmware)
Date: Thu, 29 Oct 2026 07:02:01 +0100	[thread overview]
Message-ID: <auLhWSOpMQg6cALq@eldamar.lan> (raw)
In-Reply-To: <2026-10-25-1-daily-reply-0004-bluetooth-asus-rtl8761cu-hold@kernel.org>

Hi,

On Sun, Oct 25, 2026 at 07:29:50PM -0400, Sasha Levin wrote:
> > > If it helps, I can send reverts of 980084de4d9b and 6f0624b4427e
> > > (on top of bluetooth.git master, with Cc: stable). Alternatively,
> > > btrtl could fall back to the ROM firmware when rtl8761cu_fw.bin
> > > is missing.
> > I didn't see any regression reports for 7.x releases about those
> > changes, [...] So I'm still inclined to say: leave everything as it is
> > in mainline to avoid any risk and revert only the backports of those
> > two in 6.18.y and 6.12.y.
> 
> Yup, that would be appreciated.

I'm bit lost here :) Who is now going to sen the reverts for the older
stable series? I'm bit worried that it will fall through the cracks,
but at least from Debian point of view given we want to closely follow
upstream stable releases I would pick the revert only in advance once
I know it is already as well in the stable queue for the next release.

Regards,
Salvatore

      reply	other threads:[~2026-10-29  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 15:15 [regression 6.12.y] After backport of 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") bluethooth not anymore working on 0b05:1bef ASUSTek Computer, Inc. Bluetooth Controller (requests firmware) Salvatore Bonaccorso
2026-10-04 16:29 ` Sasha Levin
2026-10-12 12:00   ` Thorsten Leemhuis
2026-10-12 17:28     ` Salvatore Bonaccorso
2026-10-13  9:03       ` Thorsten Leemhuis
2026-10-23 13:43         ` Thorsten Leemhuis
2026-10-24 14:32           ` Erik Brangs
2026-10-24 20:10           ` Sasha Levin
2026-10-25  6:16             ` Greg Kroah-Hartman
2026-10-25  6:27               ` Thorsten Leemhuis
2026-10-25  7:37                 ` Christoph Zwerschke
2026-10-25  8:07                   ` Thorsten Leemhuis
2026-10-25 23:29                     ` Sasha Levin
2026-10-29  6:02                       ` Salvatore Bonaccorso [this message]

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=auLhWSOpMQg6cALq@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1149377@bugs.debian.org \
    --cc=benh@debian.org \
    --cc=cito@online.de \
    --cc=erik.brangs@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --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