From: raghava447 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b84aa8: l2test: Fix calling getsockopt(BT_PHY)
Date: Tue, 07 Jul 2026 12:50:46 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/5bc6aa-5c1c67@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: b84aa894921037e1b1de00d282db2ee27a4ce63f
https://github.com/bluez/bluez/commit/b84aa894921037e1b1de00d282db2ee27a4ce63f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-07-07 (Tue, 07 Jul 2026)
Changed paths:
M tools/l2test.c
Log Message:
-----------
l2test: Fix calling getsockopt(BT_PHY)
getsockopt(BT_PHY) expectes a 32 bits argument not a
sizeof(struct sockaddr_l2).
Commit: 3f283c8e0ab3bad17ee8c13fa0dcf251a16e4e25
https://github.com/bluez/bluez/commit/3f283c8e0ab3bad17ee8c13fa0dcf251a16e4e25
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-07 (Tue, 07 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: 5c1c679ec304b8aadaa287cca59b38589d339e91
https://github.com/bluez/bluez/commit/5c1c679ec304b8aadaa287cca59b38589d339e91
Author: raghavendra <raghavendra.rao@collabora.com>
Date: 2026-07-07 (Tue, 07 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.
Compare: https://github.com/bluez/bluez/compare/5bc6aa79e537...5c1c679ec304
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-07 19:50 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/master/5bc6aa-5c1c67@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