From: patchwork-bot+bluetooth@kernel.org
To: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
Cc: brgl@kernel.org, marcel@holtmann.org, luiz.dentz@gmail.com,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
quic_chezhou@quicinc.com, wei.deng@oss.qualcomm.com,
jinwang.li@oss.qualcomm.com, mengshi.wu@oss.qualcomm.com,
bartosz.golaszewski@oss.qualcomm.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v7] Bluetooth: hci_qca: Fix missing wakeup during SSR memdump handling
Date: Fri, 10 Apr 2026 14:20:06 +0000 [thread overview]
Message-ID: <177583080679.2077665.8641347877052929776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260410095443.4167332-1-shuai.zhang@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 10 Apr 2026 17:54:43 +0800 you wrote:
> When a Bluetooth controller encounters a coredump, it triggers the
> Subsystem Restart (SSR) mechanism. The controller first reports the
> coredump data and, once the upload is complete, sends a hw_error
> event. The host relies on this event to proceed with subsequent
> recovery actions.
>
> If the host has not finished processing the coredump data when the
> hw_error event is received, it waits until either the processing is
> complete or the 8-second timeout expires before handling the event.
>
> [...]
Here is the summary with links:
- [v7] Bluetooth: hci_qca: Fix missing wakeup during SSR memdump handling
https://git.kernel.org/bluetooth/bluetooth-next/c/9f07d5d04826
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-04-10 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 9:54 [PATCH v7] Bluetooth: hci_qca: Fix missing wakeup during SSR memdump handling Shuai Zhang
2026-04-10 11:08 ` [v7] " bluez.test.bot
2026-04-10 14:20 ` 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=177583080679.2077665.8641347877052929776.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mengshi.wu@oss.qualcomm.com \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_chezhou@quicinc.com \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.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 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.