From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] shared/shell: Add support for -i/--init-script
Date: Sat, 25 Mar 2023 00:00:18 +0000 [thread overview]
Message-ID: <167970241887.30520.96957124269960060.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230322011349.2763404-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 Tue, 21 Mar 2023 18:13:48 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds support for -i/--init-script which can be used to provide a
> file with commands to be initialized, the commands are then run in
> sequence after completing:
>
> client/bluetoothctl -i client/power-on-off.bt
> Agent registered
> Changing power on succeeded
> [CHG] Controller A8:7E:EA:56:87:D5 Pairable: yes
> [CHG] Controller 98:8D:46:EE:6D:16 Pairable: yes
> [CHG] Controller 98:8D:46:EE:6D:16 PowerState: on-disabling
> AdvertisementMonitor path registered
>
> [...]
Here is the summary with links:
- [v2,1/2] shared/shell: Add support for -i/--init-script
(no matching commit)
- [v2,2/2] client: Add samples init scripts
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fb1c694100b2
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:[~2023-03-25 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 1:13 [PATCH v2 1/2] shared/shell: Add support for -i/--init-script Luiz Augusto von Dentz
2023-03-22 1:13 ` [PATCH v2 2/2] client: Add samples init scripts Luiz Augusto von Dentz
2023-03-22 3:38 ` [v2,1/2] shared/shell: Add support for -i/--init-script bluez.test.bot
2023-03-25 0: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=167970241887.30520.96957124269960060.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.