From: patchwork-bot+bluetooth@kernel.org
To: Hsin-chen Chuang <chharry@google.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
chromeos-bluetooth-upstreaming@chromium.org,
chharry@chromium.org, marcel@holtmann.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] Bluetooth: Remove the cmd timeout count in btusb
Date: Tue, 14 Jan 2025 17:20:37 +0000 [thread overview]
Message-ID: <173687523775.62266.15896593510934869210.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250108202442.v3.1.I66a83f84dce50455c9f7cc7b7ba8fc9d1d465db9@changeid>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 8 Jan 2025 20:24:42 +0800 you wrote:
> From: Hsin-chen Chuang <chharry@chromium.org>
>
> Remove the cmd timeout count in btusb since we only ever allow one
> command in flight at a time. We should always reset after a single
> command times out.
>
> Signed-off-by: Hsin-chen Chuang <chharry@chromium.org>
>
> [...]
Here is the summary with links:
- [v3,1/3] Bluetooth: Remove the cmd timeout count in btusb
https://git.kernel.org/bluetooth/bluetooth-next/c/e52a5e074971
- [v3,2/3] Bluetooth: Get rid of cmd_timeout and use the reset callback
https://git.kernel.org/bluetooth/bluetooth-next/c/fd224b09eedd
- [v3,3/3] Bluetooth: Allow reset via sysfs
https://git.kernel.org/bluetooth/bluetooth-next/c/c4e01540368c
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-01-14 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 12:24 [PATCH v3 1/3] Bluetooth: Remove the cmd timeout count in btusb Hsin-chen Chuang
2025-01-08 12:24 ` [PATCH v3 2/3] Bluetooth: Get rid of cmd_timeout and use the reset callback Hsin-chen Chuang
2025-01-08 12:24 ` [PATCH v3 3/3] Bluetooth: Allow reset via sysfs Hsin-chen Chuang
2025-01-08 13:17 ` [v3,1/3] Bluetooth: Remove the cmd timeout count in btusb bluez.test.bot
2025-01-14 17:20 ` 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=173687523775.62266.15896593510934869210.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chharry@chromium.org \
--cc=chharry@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.