From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
johan.hedberg@gmail.com, mmandlik@google.com,
quic_saluvala@quicinc.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: qca: Fix triggering coredump implementation
Date: Fri, 02 Feb 2024 19:10:28 +0000 [thread overview]
Message-ID: <170690102887.13805.17815962162279958410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1706259624-12518-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 Fri, 26 Jan 2024 17:00:24 +0800 you wrote:
> hci_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: 06d3fdfcdf5c ("Bluetooth: hci_qca: Add qcom devcoredump support")
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: qca: Fix triggering coredump implementation
https://git.kernel.org/bluetooth/bluetooth-next/c/5e35f82bf3f3
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-02-02 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:00 [PATCH v1] Bluetooth: qca: Fix triggering coredump implementation Zijun Hu
2024-01-26 9:33 ` [v1] " bluez.test.bot
2024-02-02 19:10 ` 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=170690102887.13805.17815962162279958410.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mmandlik@google.com \
--cc=quic_saluvala@quicinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).