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] Bluetooth: Fix possible infinite recursion of btusb_reset
Date: Tue, 21 Jan 2025 16:40:36 +0000 [thread overview]
Message-ID: <173747763674.49514.2712197702480683058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250120183938.1.I77eb26ac40229001ac90a70cb877c902456721b7@changeid>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 20 Jan 2025 18:39:39 +0800 you wrote:
> From: Hsin-chen Chuang <chharry@chromium.org>
>
> The function enters infinite recursion if the HCI device doesn't support
> GPIO reset: btusb_reset -> hdev->reset -> vendor_reset -> btusb_reset...
>
> btusb_reset shouldn't call hdev->reset after commit f07d478090b0
> ("Bluetooth: Get rid of cmd_timeout and use the reset callback")
>
> [...]
Here is the summary with links:
- Bluetooth: Fix possible infinite recursion of btusb_reset
https://git.kernel.org/bluetooth/bluetooth-next/c/9e2714de7384
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-21 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 10:39 [PATCH] Bluetooth: Fix possible infinite recursion of btusb_reset Hsin-chen Chuang
2025-01-21 16:40 ` 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=173747763674.49514.2712197702480683058.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox