From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 038ea1: shared/bap: Transition ASE to QoS Configured on CI...
Date: Sun, 14 Jun 2026 05:08:31 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1111249/000000-df5403@github.com> (raw)
Branch: refs/heads/1111249
Home: https://github.com/bluez/bluez
Commit: 038ea13b8cc1c3e46a4ef8d4956af74696470a39
https://github.com/bluez/bluez/commit/038ea13b8cc1c3e46a4ef8d4956af74696470a39
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-14 (Sun, 14 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Transition ASE to QoS Configured on CIS loss
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
Fixes PTS test BAP/USR/SCC/BV-167-C
Commit: df54038451324d0a5be729ba7cd155b5a8c0b27e
https://github.com/bluez/bluez/commit/df54038451324d0a5be729ba7cd155b5a8c0b27e
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-14 (Sun, 14 Jun 2026)
Changed paths:
M unit/test-bap.c
Log Message:
-----------
unit/bap: Add CIS loss test
Verify a Source ASE in the Enabling state transitions to QoS Configured
rather than Disabling when its CIS is lost.
Assisted-by: ClaudeCode:claude-opus-4.8
Compare: https://github.com/bluez/bluez/compare/038ea13b8cc1%5E...df5403845132
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-14 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1111249/000000-df5403@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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