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/5] tools: Use '>' as prompt end marker
Date: Thu, 12 Dec 2024 18:10:32 +0000 [thread overview]
Message-ID: <173402703274.2391244.9155452097327964395.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241211192210.1864347-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 Wed, 11 Dec 2024 14:22:06 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This replaces the use of '#' with '>' as prompt end marker since the
> former is used to describe comments on the script which might be
> confused with prompt.
> ---
> client/main.c | 6 +++---
> client/mgmt.c | 6 +++---
> tools/bluetooth-player.c | 2 +-
> tools/btpclientctl.c | 2 +-
> tools/mesh-cfgclient.c | 2 +-
> tools/mesh-gatt/util.c | 2 +-
> tools/mesh/util.c | 2 +-
> tools/meshctl.c | 4 ++--
> 8 files changed, 13 insertions(+), 13 deletions(-)
Here is the summary with links:
- [BlueZ,v2,1/5] tools: Use '>' as prompt end marker
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5f0ec38851e1
- [BlueZ,v2,2/5] bluetoothctl: Update documentation to use '>' as prompt end marker
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d1eb37042d9d
- [BlueZ,v2,3/5] share/hci: Introduce bt_hci_send_data
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=560dcd2ea3d2
- [BlueZ,v2,4/5] client: Add HCI submenu
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5527c88bc717
- [BlueZ,v2,5/5] client: Add bluetoothctl-hci.1 man page
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6905331e2cd8
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:[~2024-12-12 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 19:22 [PATCH BlueZ v2 1/5] tools: Use '>' as prompt end marker Luiz Augusto von Dentz
2024-12-11 19:22 ` [PATCH BlueZ v2 2/5] bluetoothctl: Update documentation to use " Luiz Augusto von Dentz
2024-12-11 19:22 ` [PATCH BlueZ v2 3/5] share/hci: Introduce bt_hci_send_data Luiz Augusto von Dentz
2024-12-11 19:22 ` [PATCH BlueZ v2 4/5] client: Add HCI submenu Luiz Augusto von Dentz
2024-12-11 19:22 ` [PATCH BlueZ v2 5/5] client: Add bluetoothctl-hci.1 man page Luiz Augusto von Dentz
2024-12-11 20:32 ` [BlueZ,v2,1/5] tools: Use '>' as prompt end marker bluez.test.bot
2024-12-12 18:10 ` 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=173402703274.2391244.9155452097327964395.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).