From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 928fa9: shared/bap: Fix endpoint configuration
Date: Mon, 23 Feb 2026 04:55:03 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1056469/000000-928fa9@github.com> (raw)
Branch: refs/heads/1056469
Home: https://github.com/bluez/bluez
Commit: 928fa9eb095d4fef96668541b17312e5800d6de2
https://github.com/bluez/bluez/commit/928fa9eb095d4fef96668541b17312e5800d6de2
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-02-23 (Mon, 23 Feb 2026)
Changed paths:
M profiles/audio/media.c
M src/shared/bap.c
M src/shared/bap.h
Log Message:
-----------
shared/bap: Fix endpoint configuration
When a first local endpoint is created after connection to a remote
device this doesn't trigger the SelectProperties request because
bt_bap_bac ops are not yet set when bt_bap_select() is called.
Creating a second local endpoint allows to trigger SelectProperties
request for the first endpoint.
This commit fixes this behavior by setting the ops during bt_bap_pac
creation.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-02-23 12: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/1056469/000000-928fa9@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