From: patchwork-bot+bluetooth@kernel.org
To: Tim Jiang (QUIC) <quic_tjiang@quicinc.com>
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
quic_bgodavar@quicinc.com, quic_hemantg@quicinc.com,
mka@chromium.org
Subject: Re: [PATCH v3] Bluetooth: btusb: Add WCN6855 devcoredump support
Date: Thu, 20 Apr 2023 21:00:20 +0000 [thread overview]
Message-ID: <168202442066.11865.5106451617006072120.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230419033805.27356-1-quic_tjiang@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 19 Apr 2023 11:38:05 +0800 you wrote:
> WCN6855 will report memdump via ACL data or HCI event when
> it get crashed, so we collect memdump to debug firmware.
>
> Signed-off-by: Tim Jiang <quic_tjiang@quicinc.com>
> ---
> drivers/bluetooth/btusb.c | 222 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 222 insertions(+)
Here is the summary with links:
- [v3] Bluetooth: btusb: Add WCN6855 devcoredump support
https://git.kernel.org/bluetooth/bluetooth-next/c/8c70acc21f68
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:[~2023-04-20 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 3:38 [PATCH v3] Bluetooth: btusb: Add WCN6855 devcoredump support Tim Jiang
2023-04-19 4:35 ` [v3] " bluez.test.bot
2023-04-19 7:22 ` [PATCH v3] " Paul Menzel
2023-04-19 8:01 ` Tim Jiang (QUIC)
2023-04-20 21:00 ` 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=168202442066.11865.5106451617006072120.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hemantg@quicinc.com \
--cc=quic_tjiang@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