From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ 0/3] Fix bluetoothctl hanging if daemon isn't running
Date: Tue, 17 Sep 2024 14:30:30 +0000 [thread overview]
Message-ID: <172658343027.158268.11140300702959343294.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240912092253.119754-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 12 Sep 2024 11:20:09 +0200 you wrote:
> Our QE folks have run into this problem multiple times. The problem seems
> to have existed since at least 5.56.
>
> Bastien Nocera (3):
> shared/shell: Add bt_shell_get_timeout()
> client: Respect --timeout when bluetoothd isn't running
> shared/shell: Exit after printing the help
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] shared/shell: Add bt_shell_get_timeout()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1428d8461e92
- [BlueZ,2/3] client: Respect --timeout when bluetoothd isn't running
(no matching commit)
- [BlueZ,3/3] shared/shell: Exit after printing the help
(no matching commit)
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-09-17 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 9:20 [BlueZ 0/3] Fix bluetoothctl hanging if daemon isn't running Bastien Nocera
2024-09-12 9:20 ` [BlueZ 1/3] shared/shell: Add bt_shell_get_timeout() Bastien Nocera
2024-09-12 11:58 ` Fix bluetoothctl hanging if daemon isn't running bluez.test.bot
2024-09-12 9:20 ` [BlueZ 2/3] client: Respect --timeout when bluetoothd " Bastien Nocera
2024-09-12 9:20 ` [BlueZ 3/3] shared/shell: Exit after printing the help Bastien Nocera
2024-09-12 15:11 ` Luiz Augusto von Dentz
2024-09-12 16:13 ` Bastien Nocera
2024-10-22 12:24 ` Bastien Nocera
2024-09-17 14:30 ` 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=172658343027.158268.11140300702959343294.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--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 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.