From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 97431a: client/btpclient: Improve GATT read
Date: Wed, 23 Sep 2026 14:49:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f26da4-8b4a41@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 97431abc432fde861f180f5ada31c8c503bd93b2
https://github.com/bluez/bluez/commit/97431abc432fde861f180f5ada31c8c503bd93b2
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-09-23 (Wed, 23 Sep 2026)
Changed paths:
M client/btpclient/gatt.c
Log Message:
-----------
client/btpclient: Improve GATT read
BAP/UCL/CGITT/* tests request to read the different Sink/Source
Audio Stream Endpoint characteristics.
The first ReadValue call triggers read of the other characteristics
and PTS, which tracks the read requests, may disconnect before the
following explicit ReadValue has been replied.
First try to read the characteristic value from the proxy cache
before calling ReadValue explicitly.
Commit: 8b4a4176063831476bc9244d20f43b552e4b5554
https://github.com/bluez/bluez/commit/8b4a4176063831476bc9244d20f43b552e4b5554
Author: Jinwang Li <jinwang.li@oss.qualcomm.com>
Date: 2026-09-23 (Wed, 23 Sep 2026)
Changed paths:
M obexd/client/pbap.c
Log Message:
-----------
obexd/pbap: Fix u128_to_string skipping data[4]
u128_to_string uses data[3] twice causing data[4] to be skipped and
DatabaseIdentifier, PrimaryCounter and SecondaryCounter properties to
be printed with wrong values.
Fixes: 5ee26d43c65c ("obexd/client: Add DatabaseIdentifier property")
Assisted-by: opencode:claude-sonnet-5
Signed-off-by: Jinwang Li <jinwang.li@oss.qualcomm.com>
Compare: https://github.com/bluez/bluez/compare/f26da4389e2d...8b4a41760638
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-23 21:49 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/f26da4-8b4a41@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.