From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] f8fd83: avdtp: Add GetConfiguration DBus function
Date: Mon, 08 Jun 2026 07:55:51 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1107804/000000-12ee17@github.com> (raw)
Branch: refs/heads/1107804
Home: https://github.com/bluez/bluez
Commit: f8fd83da41d0f7478ef4748b7aef68f7fab4ea60
https://github.com/bluez/bluez/commit/f8fd83da41d0f7478ef4748b7aef68f7fab4ea60
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M profiles/audio/a2dp.c
M profiles/audio/avdtp.c
M profiles/audio/avdtp.h
Log Message:
-----------
avdtp: Add GetConfiguration DBus function
Change avdtp_get_configuration to accept remote SEP instead of stream a
and add an async callback for response/reject handling; the old function
was not used anywhere (unit-test just copied signature), so it was
changed in place.
Add a GetConfiguration async D-Bus method to the remote SEP interface that
returns the retrieved configuration as a byte array.
This can be used to pass: AVDTP/SRC/INT/SIG/SMG/BV-11-C
Commit: 12ee17f9ca7eab2b4b210e7c2fc004c4e868a9bf
https://github.com/bluez/bluez/commit/12ee17f9ca7eab2b4b210e7c2fc004c4e868a9bf
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M client/player.c
M doc/bluetoothctl-endpoint.rst
M doc/org.bluez.MediaEndpoint.rst
Log Message:
-----------
client/player: Add get-config command
Compare: https://github.com/bluez/bluez/compare/f8fd83da41d0%5E...12ee17f9ca7e
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-08 14:55 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/1107804/000000-12ee17@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