From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] shared/bap: handle inverted order of stop ready and disabling->qos
Date: Mon, 23 Jun 2025 17:20:05 +0000 [thread overview]
Message-ID: <175069920525.3239463.10574050638683479754.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c98a6f523b122b47aaffb3ff6b59ccb236d76749.1750592769.git.pav@iki.fi>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 22 Jun 2025 14:48:02 +0300 you wrote:
> DISABLING->QOS transition and Receiver Stop Ready reply may arrive in
> any order. BAP v1.0.2 (Sec. 5.6.5.1): CIS may be terminated by either
> side after Receiver Stop Ready has successfully completed. However,
> when we get the reply, the stream may be in either state.
>
> Instead of client detaching the IO on stop ready reply, rely on
> detaching IO on entering QOS, where Receiver Stop Ready has then
> necessarily completed. On DISABLING, mark stream io as not connecting,
> so that it gets detached even if CIS was not yet established.
>
> [...]
Here is the summary with links:
- [BlueZ] shared/bap: handle inverted order of stop ready and disabling->qos
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ae1b7f6ba805
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-06-23 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 11:48 [PATCH BlueZ] shared/bap: handle inverted order of stop ready and disabling->qos Pauli Virtanen
2025-06-22 13:12 ` [BlueZ] " bluez.test.bot
2025-06-23 17: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=175069920525.3239463.10574050638683479754.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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