From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 486fb1: shared/shell: Add support for -EINPROGRESS to bt_s...
Date: Thu, 05 Jun 2025 12:34:44 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/969046/000000-c5ff04@github.com> (raw)
Branch: refs/heads/969046
Home: https://github.com/bluez/bluez
Commit: 486fb1f757fc4f91353686ebf2aa34524b8424d6
https://github.com/bluez/bluez/commit/486fb1f757fc4f91353686ebf2aa34524b8424d6
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-06-05 (Thu, 05 Jun 2025)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: Add support for -EINPROGRESS to bt_shell_noninteractive_quit
This enables commands to call bt_shell_noninteractive_quit with status
set to -EINPROGRESS to indicate their execution is in progress and shall
not exit in case of MODE_NONINTERACTIVE but it can proceed to the next
command for MODE_INTERACTIVE.
Commit: c5ff043720daba670452c0cc913239fdbd1e5433
https://github.com/bluez/bluez/commit/c5ff043720daba670452c0cc913239fdbd1e5433
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-06-05 (Thu, 05 Jun 2025)
Changed paths:
M client/advertising.c
M client/main.c
Log Message:
-----------
client: Use -EINPROGRESS with scan and advertise command
This uses -EINPROGRESS with commands scan and advertise since they need
to keep running in the background so they don't exit but shouldn't block
other command from executing in case they are invoked from a script.
Compare: https://github.com/bluez/bluez/compare/486fb1f757fc%5E...c5ff043720da
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-06-05 19:34 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/969046/000000-c5ff04@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