From: patchwork-bot+bluetooth@kernel.org
To: Junjie Cao <junjie.cao@intel.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
andrew.tsvetinskiy@gmail.com, kserwus@gmail.com,
alexej@sidorenko.cz, regressions@leemhuis.info,
linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728
Date: Tue, 29 Sep 2026 15:40:06 +0000 [thread overview]
Message-ID: <179069640603.997963.8086437204230046339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260920020227.709800-1-junjie.cao@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 20 Sep 2026 10:02:27 +0800 you wrote:
> Commit 5ead2063611a ("Bluetooth: btrtl: fix RTL8761B/BU broken LE
> extended scan") set HCI_QUIRK_BROKEN_EXT_SCAN on every RTL8761B, and
> commit ca0583c24661 ("Bluetooth: btusb: limit RTL8761B BROKEN_EXT_SCAN
> quirk to 0bda:a728") kept it on 0bda:a728 on the assumption that the
> USB id separates dongles with broken extended scan from those with a
> broken legacy scan path. It does not. An 0bda:a728 unit (RTL8761BUV,
> fw 0xdfc6d922) on 6.18.51 fails the same way the UB500 and 0bda:8771
> did: LE Set Scan Enable (0x200c) times out with -110 and btusb resets
> the device. With the flag removed from the table entry, scanning works
> on that unit.
>
> [...]
Here is the summary with links:
- Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728
https://git.kernel.org/bluetooth/bluetooth-next/c/fdd5964bd389
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-29 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:02 [PATCH] Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728 Junjie Cao
2026-09-20 7:36 ` bluez.test.bot
2026-09-29 15:40 ` patchwork-bot+bluetooth [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=179069640603.997963.8086437204230046339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alexej@sidorenko.cz \
--cc=andrew.tsvetinskiy@gmail.com \
--cc=junjie.cao@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.