From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] Bluetooth: btusb: Fix triggering coredump implementation for QCA
Date: Thu, 11 Apr 2024 14:39:43 +0000 [thread overview]
Message-ID: <171284638322.18150.7773628914846691694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1711354309-27605-1-git-send-email-quic_zijuhu@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 25 Mar 2024 16:11:49 +0800 you wrote:
> btusb_coredump_qca() uses __hci_cmd_sync() to send a vendor-specific
> command to trigger firmware coredump, but the command does not
> have any event as its sync response, so it is not suitable to use
> __hci_cmd_sync(), fixed by using __hci_cmd_send().
>
> Fixes: 20981ce2d5a5 ("Bluetooth: btusb: Add WCN6855 devcoredump support")
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>
> [...]
Here is the summary with links:
- [v2,RESEND] Bluetooth: btusb: Fix triggering coredump implementation for QCA
https://git.kernel.org/bluetooth/bluetooth-next/c/e00fc2700a3f
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-04-11 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 5:14 [PATCH v1] Bluetooth: btusb: Fix triggering coredump implementation for QCA Zijun Hu
2024-02-04 6:07 ` [v1] " bluez.test.bot
2024-02-23 2:46 ` [PATCH v2] " Zijun Hu
2024-03-25 8:11 ` [PATCH v2 RESEND] " Zijun Hu
2024-03-25 10:57 ` [v2,RESEND] " bluez.test.bot
2024-04-11 14:39 ` 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=171284638322.18150.7773628914846691694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_zijuhu@quicinc.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.