From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] f863d0: gatt-client: allow AcquireNotify when characterist...
Date: Mon, 18 Nov 2024 09:38:20 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/95e89c-da0253@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: f863d0116d6271585c2521ff18447c95d95f82fd
https://github.com/bluez/bluez/commit/f863d0116d6271585c2521ff18447c95d95f82fd
Author: Benedek Kupper <benedek.kupper@epitome.inc>
Date: 2024-11-18 (Mon, 18 Nov 2024)
Changed paths:
M src/gatt-client.c
Log Message:
-----------
gatt-client: allow AcquireNotify when characteristic has indicate flag
StartNotify / StopNotify already correctly allows usage when the
characteristic indicate is present (simplify this check though),
apply the same to AcquireNotify.
Fixes: https://github.com/bluez/bluez/issues/1022
Commit: da0253959ec384d8c4ff7c970ce12fb8a95bd052
https://github.com/bluez/bluez/commit/da0253959ec384d8c4ff7c970ce12fb8a95bd052
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-11-18 (Mon, 18 Nov 2024)
Changed paths:
M doc/org.bluez.GattCharacteristic.rst
Log Message:
-----------
org.bluez.GattCharacteristic: Update documentation of AcquireNotify
This updates the documentation of AcquireNotify adding that indicate
flag also allows the usage of AcquireNotify.
Compare: https://github.com/bluez/bluez/compare/95e89cd2e4f8...da0253959ec3
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-11-18 17:38 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/95e89c-da0253@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.