From: Sasha Levin <sashal@kernel.org>
To: linux-bluetooth@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Alexej Sidorenko <alexej@sidorenko.cz>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
Kamil Serwus <kserwus@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "Bluetooth: btrtl: fix RTL8761B/BU broken LE extended scan"
Date: Tue, 25 Aug 2026 07:49:29 -0400 [thread overview]
Message-ID: <202608250008.c25c563b74024d19@kernel.org> (raw)
In-Reply-To: <20260823102959.100368-1-kserwus@gmail.com>
On Sun, Aug 23, 2026 at 12:29:59PM +0200, Kamil Serwus wrote:
> This reverts commit 5ead2063611ae56809b1b113ac44cef9547c81d7.
>
> It sets HCI_QUIRK_BROKEN_EXT_SCAN for every CHIP_ID_8761B, which forces
> the legacy LE Set Scan Enable command (0x200c). That was validated on one
> dongle, USB 0bda:a728, and it breaks others sharing the chip id
5ead2063611a ("Bluetooth: btrtl: fix RTL8761B/BU broken LE extended
scan") is still in mainline, so I'd rather not carry a stable-only revert
ahead of it - that would just make the stable trees diverge from Linus'.
Please get the revert (or the detection-based fix under discussion)
merged upstream. Once it is in mainline with a stable tag we will pick it
up for 7.1.y and 6.18.y the normal way.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-25 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 10:29 [PATCH] Revert "Bluetooth: btrtl: fix RTL8761B/BU broken LE extended scan" Kamil Serwus
2026-08-25 11:49 ` Sasha Levin [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=202608250008.c25c563b74024d19@kernel.org \
--to=sashal@kernel.org \
--cc=alexej@sidorenko.cz \
--cc=kserwus@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=regressions@leemhuis.info \
--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