From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: Reject user coredump until firmware is operational
Date: Thu, 19 Nov 2026 18:30:05 +0000 [thread overview]
Message-ID: <179511300528.3261689.3188065362433475885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118232043.1987049-1-kiran.k@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 19 Nov 2026 04:50:43 +0530 you wrote:
> A user can request a device coredump through the PCI coredump sysfs
> attribute at any time, including while firmware is being downloaded
> from btintel_pcie_setup(). The request then rings the DBGC flush
> doorbell on bootloader firmware that does not service it, or, if the
> core halted, reads debug regions under MAC access while the setup
> retry path is resetting and re-enabling the device.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel_pcie: Reject user coredump until firmware is operational
https://git.kernel.org/bluetooth/bluetooth-next/c/cb60e0e5df95
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:[~2026-11-19 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 23:20 [PATCH v1] Bluetooth: btintel_pcie: Reject user coredump until firmware is operational Kiran K
2026-11-19 0:59 ` [v1] " bluez.test.bot
2026-11-19 18:30 ` 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=179511300528.3261689.3188065362433475885.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.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.