From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e9f2c8: shared/mcp: emit MCS error if value changes during...
Date: Tue, 13 Jan 2026 14:42:30 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/a94f99-4ce4b5@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e9f2c8fdc676e8d33ed1a3be144594ebdfb620de
https://github.com/bluez/bluez/commit/e9f2c8fdc676e8d33ed1a3be144594ebdfb620de
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-01-13 (Tue, 13 Jan 2026)
Changed paths:
M src/shared/mcp.c
Log Message:
-----------
shared/mcp: emit MCS error if value changes during long read
MCS spec requires emitting Value Changed During Read Long if value
changes between remote reading with zero offset and nonzero offset.
This is session-specific state, so add support for that.
As server, track value changes and emit that error properly.
As client, we don't need to reread if this error occurs, as there should
be a notification or track changed that queues a new read.
Commit: 4ce4b5d679ab62bc6361207c67007e9e6df22779
https://github.com/bluez/bluez/commit/4ce4b5d679ab62bc6361207c67007e9e6df22779
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-01-13 (Tue, 13 Jan 2026)
Changed paths:
M src/shared/mcp.c
M src/shared/mcp.h
M unit/test-mcp.c
Log Message:
-----------
test-mcp: add tests for long value reading
Add server tests for handling the Value Changed During Read Long error.
Add similar client tests.
Compare: https://github.com/bluez/bluez/compare/a94f994201a6...4ce4b5d679ab
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-01-13 22:42 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/a94f99-4ce4b5@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