From: patchwork-bot+bluetooth@kernel.org
To: Simon Mikuda <simon.mikuda@streamunlimited.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] shared/bap: Transition ASE to QoS Configured on CIS loss
Date: Mon, 15 Jun 2026 15:20:08 +0000 [thread overview]
Message-ID: <178153680863.3644727.3015101124528960748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260614100208.1091560-1-simon.mikuda@streamunlimited.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 14 Jun 2026 12:02:07 +0200 you wrote:
> stream_io_disconnected() only handled the Releasing state, leaving
> Enabling, Streaming and Disabling ASEs stuck when the CIS was lost
> unexpectedly.
>
> The ASE shall autonomously move to QoS Configured on loss of the
> CIS and notify the peer
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] shared/bap: Transition ASE to QoS Configured on CIS loss
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=237d4d5d20a5
- [BlueZ,v2,2/2] unit/bap: Add CIS loss test
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=986e220b77ea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-15 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 21:11 [PATCH BlueZ] shared/bap: Transition ASE to QoS Configured on CIS loss Simon Mikuda
2026-06-09 22:15 ` Pauli Virtanen
2026-06-10 7:57 ` Simon Mikuda
2026-06-10 13:10 ` Luiz Augusto von Dentz
2026-06-14 10:02 ` [PATCH BlueZ v2 1/2] " Simon Mikuda
2026-06-14 10:02 ` [PATCH BlueZ v2 2/2] unit/bap: Add CIS loss test Simon Mikuda
2026-06-14 13:12 ` [BlueZ,v2,1/2] shared/bap: Transition ASE to QoS Configured on CIS loss bluez.test.bot
2026-06-15 15:20 ` patchwork-bot+bluetooth [this message]
2026-06-09 23:02 ` [BlueZ] " bluez.test.bot
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=178153680863.3644727.3015101124528960748.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox