From: raghava447 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7ab771: shared/bap: Validate codec configuration parameters
Date: Thu, 02 Jul 2026 08:24:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1120502/000000-a38052@github.com> (raw)
Branch: refs/heads/1120502
Home: https://github.com/bluez/bluez
Commit: 7ab7714c80737f7fab71d1ab083274cf257cb341
https://github.com/bluez/bluez/commit/7ab7714c80737f7fab71d1ab083274cf257cb341
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-02 (Thu, 02 Jul 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Validate codec configuration parameters
This is required for PTS test ASCS/SR/SPE/BI-07-C
Commit: 6e4d8000b49b493c05a4fa3d1025224199cc4990
https://github.com/bluez/bluez/commit/6e4d8000b49b493c05a4fa3d1025224199cc4990
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-02 (Thu, 02 Jul 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Validate unicast QoS configuration
This is required for PTS tests ASCS/SR/SPE/BI-08-C and ASCS/SR/SPE/BI-10-C.
Commit: e0e3fca8500f260b1c4b43ca9cad84c0856833b6
https://github.com/bluez/bluez/commit/e0e3fca8500f260b1c4b43ca9cad84c0856833b6
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-02 (Thu, 02 Jul 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Handle ASCS control point protocol errors
This is required for PTS tests ASCS/SR/SPE/BI-01-C and ASCS/SR/SPE/BI-09-C.
Commit: a3805221ac641d8a28f02033874df1e1ee79e15e
https://github.com/bluez/bluez/commit/a3805221ac641d8a28f02033874df1e1ee79e15e
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-02 (Thu, 02 Jul 2026)
Changed paths:
M unit/test-bap.c
Log Message:
-----------
unit/bap: Add invalid ASCS control point tests
Adds coverage for PTS tests ASCS/SR/SPE/BI-01-C and BI-07-C to BI-10-C.
Compare: https://github.com/bluez/bluez/compare/7ab7714c8073%5E...a3805221ac64
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-02 15:24 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/1120502/000000-a38052@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