All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH] adapter: Fix Discovering staying true after a rejected stop
Date: Wed, 28 Oct 2026 19:50:20 +0000	[thread overview]
Message-ID: <179321702006.1394536.2604695616484204299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027160852.54689-1-kevin@simpleble.org>

Hello:

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

On Tue, 27 Oct 2026 09:08:52 -0700 you wrote:
> The kernel rejects Stop Discovery when no discovery is active by the
> time it processes the command, because the discovery ended or another
> mgmt client stopped it just before. stop_discovery_complete() then
> removes the client but keeps the discovery state, so Discovering stays
> true with no client left, and the next StartDiscovery with the same
> filter returns without starting a discovery. The client that called
> StopDiscovery also gets an InProgress error, and "No discovery started"
> if it tries again.
> 
> [...]

Here is the summary with links:
  - adapter: Fix Discovering staying true after a rejected stop
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4f3428e9df2f

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



      parent reply	other threads:[~2026-10-28 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 16:08 [PATCH] adapter: Fix Discovering staying true after a rejected stop Kevin Dewald
2026-10-27 17:42 ` Kevin Dewald
2026-10-27 20:30 ` bluez.test.bot
2026-10-28 19:50 ` 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=179321702006.1394536.2604695616484204299.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=kevin@simpleble.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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.