From: patchwork-bot+bluetooth@kernel.org
To: Hilda Wu <hildawu@realtek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, mmandlik@google.com,
apusaka@chromium.org, yinghsu@chromium.org,
alex_lu@realsil.com.cn, max.chou@realtek.com, kidman@realtek.com
Subject: Re: [PATCH v4] Bluetooth: btrtl: Add Realtek devcoredump support
Date: Tue, 23 May 2023 17:40:21 +0000 [thread overview]
Message-ID: <168486362152.30009.17829530395112932245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230427032755.28519-1-hildawu@realtek.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 27 Apr 2023 11:27:55 +0800 you wrote:
> From: Hilda Wu <hildawu@realtek.com>
>
> Catch debug exception from controller and driver, and trigger a
> devcoredump using hci devcoredump APIs. The debug exception data
> will be parsed in userspace.
>
> Signed-off-by: Alex Lu <alex_lu@realsil.com.cn>
> Signed-off-by: Hilda Wu <hildawu@realtek.com>
>
> [...]
Here is the summary with links:
- [v4] Bluetooth: btrtl: Add Realtek devcoredump support
https://git.kernel.org/bluetooth/bluetooth-next/c/ab93c2a34458
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-05-23 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 3:27 [PATCH v4] Bluetooth: btrtl: Add Realtek devcoredump support hildawu
2023-04-27 4:00 ` [v4] " bluez.test.bot
2023-05-22 6:02 ` [PATCH v4] " Hilda Wu
2023-05-23 17: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=168486362152.30009.17829530395112932245.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex_lu@realsil.com.cn \
--cc=apusaka@chromium.org \
--cc=hildawu@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=mmandlik@google.com \
--cc=yinghsu@chromium.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.