From: "Šimon Mikuda" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 19245b: gatt-client: Add PreferredNotifyType property
Date: Mon, 08 Jun 2026 07:55:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1107894/000000-19245b@github.com> (raw)
Branch: refs/heads/1107894
Home: https://github.com/bluez/bluez
Commit: 19245b27a229da41b4c5f417dc544bbf2f87b46b
https://github.com/bluez/bluez/commit/19245b27a229da41b4c5f417dc544bbf2f87b46b
Author: Simon Mikuda <simon.mikuda@streamunlimited.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M doc/org.bluez.GattCharacteristic.rst
M src/gatt-client.c
M src/shared/gatt-client.c
M src/shared/gatt-client.h
Log Message:
-----------
gatt-client: Add PreferredNotifyType property
When a characteristic supports both notifications and indications the
CCC we always register for notifications, leaving no way to choose
indications from D-Bus.
Add PreferredNotifyType (string, "notification"/"indication") to
org.bluez.GattCharacteristic1, only present when both flags are set.
StartNotify() and AcquireNotify() honor it on the next CCC write.
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/1107894/000000-19245b@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