From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] shared/shell: Add support for -EINPROGRESS to bt_shell_noninteractive_quit
Date: Fri, 06 Jun 2025 19:00:29 +0000 [thread overview]
Message-ID: <174923642999.3945689.12926721012930977900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250605192406.909397-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 5 Jun 2025 15:24:05 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> 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.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] shared/shell: Add support for -EINPROGRESS to bt_shell_noninteractive_quit
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7d59391bb783
- [BlueZ,v2,2/2] client: Use -EINPROGRESS with scan and advertise command
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5499681bc632
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-06 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 19:24 [PATCH BlueZ v2 1/2] shared/shell: Add support for -EINPROGRESS to bt_shell_noninteractive_quit Luiz Augusto von Dentz
2025-06-05 19:24 ` [PATCH BlueZ v2 2/2] client: Use -EINPROGRESS with scan and advertise command Luiz Augusto von Dentz
2025-06-05 20:51 ` [BlueZ,v2,1/2] shared/shell: Add support for -EINPROGRESS to bt_shell_noninteractive_quit bluez.test.bot
2025-06-06 19:00 ` patchwork-bot+bluetooth [this message]
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=174923642999.3945689.12926721012930977900.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.