From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a69ae4: client: Fix gatt.{read, write} not working on scripts
Date: Mon, 21 Jul 2025 13:16:49 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/984445/000000-a69ae4@github.com> (raw)
Branch: refs/heads/984445
Home: https://github.com/bluez/bluez
Commit: a69ae4d1fc3ec3b60e7649977340a0966c7b1efa
https://github.com/bluez/bluez/commit/a69ae4d1fc3ec3b60e7649977340a0966c7b1efa
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-07-21 (Mon, 21 Jul 2025)
Changed paths:
M client/gatt.c
Log Message:
-----------
client: Fix gatt.{read, write} not working on scripts
If gatt.{read, write} are called within a script they don't indicate
completion so they block commands to be run after them.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-21 20:16 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/984445/000000-a69ae4@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