From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a08983: shared/bap: Fix not handling read offset
Date: Tue, 27 May 2025 06:40:38 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/966677/000000-a08983@github.com> (raw)
Branch: refs/heads/966677
Home: https://github.com/bluez/bluez
Commit: a089831e49937230a2bafd94b356d07ec5628b48
https://github.com/bluez/bluez/commit/a089831e49937230a2bafd94b356d07ec5628b48
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-05-27 (Tue, 27 May 2025)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Fix not handling read offset
Some attributes may need to handle offset other than 0 in case read long
procedure is used, so this properly handles that for PAC_SINK_CHRC_UUID
and PAC_SOURCE_CHRC_UUID.
In addition to PAC record this also uses
gatt_db_attribute_set_fixed_length for attributes that are considered of
fixed size so gatt_db can handle offset directly.
Fixes: https://github.com/bluez/bluez/issues/1294
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-27 13:40 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/966677/000000-a08983@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.