Re: [PATCH BlueZ 0/2] adapter: Fix Discovering staying true when stopping fails

[patchwork-bot+bluetooth@kernel.org]

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 27 Oct 2026 10:19:21 -0700 you wrote:
> When the Stop Discovery bluetoothd sends for the last discovery client
> fails, stop_discovery_complete() removes the client but leaves
> Discovering true. The next StartDiscovery with the same filter then
> returns success without starting a discovery, as reported in
> bluez/bluez#2547 and, before it, #807.
> 
> The first patch treats Rejected as stopped: the kernel returns it when
> the discovery already ended, or another mgmt client stopped it, just
> before the command was processed. The second clears Discovering when
> the kernel reports the discovery as stopped with no client left, which
> covers the other failures, such as the scan disable timing out. That
> needs the kernel to leave the stopping state after a failed stop, which
> "Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery",
> posted separately, does.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/2] adapter: Fix Discovering staying true after a rejected stop
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4f3428e9df2f
  - [BlueZ,2/2] adapter: Fix Discovering staying true after a failed stop
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html