From: patchwork-bot+bluetooth@kernel.org
To: Manish Mandlik <mmandlik@google.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org,
chromeos-bluetooth-upstreaming@chromium.org
Subject: Re: [BlueZ PATCH v5 1/2] vhci: Add support to trigger devcoredump and read the dump file
Date: Thu, 30 Mar 2023 18:10:25 +0000 [thread overview]
Message-ID: <168019982520.20045.11650139439500360979.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230329230734.BlueZ.v5.1.I21ac5a143b0e42eef4ff71ef04ef0e53a294932a@changeid>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 29 Mar 2023 23:08:02 -0700 you wrote:
> Add vhci support to trigger the hci devcoredump by writing to
> force_devcoredump debugfs entry and read the generated devcoredump
> file.
>
> ---
>
> Changes in v5:
> - Refactor vhci_read_devcd()
>
> [...]
Here is the summary with links:
- [BlueZ,v5,1/2] vhci: Add support to trigger devcoredump and read the dump file
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8bd2f2961774
- [BlueZ,v5,2/2] mgmt-tester: Add devcoredump tests
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-30 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 6:08 [BlueZ PATCH v5 1/2] vhci: Add support to trigger devcoredump and read the dump file Manish Mandlik
2023-03-30 6:08 ` [BlueZ PATCH v5 2/2] mgmt-tester: Add devcoredump tests Manish Mandlik
2023-03-30 7:28 ` [BlueZ,v5,1/2] vhci: Add support to trigger devcoredump and read the dump file bluez.test.bot
2023-03-30 18:10 ` patchwork-bot+bluetooth [this message]
2023-03-30 18:18 ` [BlueZ PATCH v5 1/2] " Luiz Augusto von Dentz
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=168019982520.20045.11650139439500360979.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mmandlik@google.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