From: patchwork-bot+bluetooth@kernel.org
To: Ye He <ye.he@amlogic.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH bluez v2] adapter: Fix RemoveDevice timeout when device already disconnected
Date: Tue, 15 Jul 2025 14:50:07 +0000 [thread overview]
Message-ID: <175259100774.468243.11042910246929634168.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715-adapter-rm-device-v2-1-f0ab3cc19391@amlogic.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 15 Jul 2025 17:28:20 +0800 you wrote:
> From: Ye He <ye.he@amlogic.com>
>
> When attempting to use RemoveDevice to delete a BIS source device that
> was synchronized by the BIS sink scan delegator, the kernel marks the
> device as disconnected due to PA(period adv) sync termination. However, BlueZ is not
> notified of this disconnection and still proceeds to send MGMT Disconnect
> command. The kernel responds with MGMT_STATUS_DISCONNECTED, which BlueZ
> does not currently handle as a successful case. As a result, the RemoveDevice
> call never completes and no D-Bus reply is returned.
>
> [...]
Here is the summary with links:
- [bluez,v2] adapter: Fix RemoveDevice timeout when device already disconnected
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8c9977b02169
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:[~2025-07-15 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:28 [PATCH bluez v2] adapter: Fix RemoveDevice timeout when device already disconnected Ye He
2025-07-15 9:28 ` Ye He via B4 Relay
2025-07-15 10:58 ` [bluez,v2] " bluez.test.bot
2025-07-15 14: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=175259100774.468243.11042910246929634168.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ye.he@amlogic.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.