From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery
Date: Mon, 02 Nov 2026 22:20:18 +0000 [thread overview]
Message-ID: <179365801804.694758.16698757063901481997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102170000.62469-1-kevin@simpleble.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 2 Nov 2026 09:00:00 -0800 you wrote:
> Stop Discovery moves the discovery to DISCOVERY_STOPPING, and
> stop_discovery_complete() only moves it on to DISCOVERY_STOPPED when
> stopping succeeded. When it fails, for example because LE Set Scan
> Enable times out, nothing moves the discovery out of
> DISCOVERY_STOPPING: Stop Discovery is rejected, as the discovery is not
> active anymore, and the LE scan timeout was cancelled before the scan
> was disabled. Until the controller is powered off, every Start
> Discovery then fails with Busy, and hci_update_passive_scan_sync()
> skips background scanning, so devices set to auto-connect are not
> connected anymore.
>
> [...]
Here is the summary with links:
- [v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery
https://git.kernel.org/bluetooth/bluetooth-next/c/60b10121db60
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-11-02 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 17:00 [PATCH v5] Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery Kevin Dewald
2026-11-02 19:36 ` [v5] " bluez.test.bot
2026-11-02 22:20 ` 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=179365801804.694758.16698757063901481997.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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