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
Subject: Re: [PATCH v7 0/1] Bluetooth: btqca: move WCN7850 WA
Date: Tue, 06 Jan 2026 18:21:10 +0000 [thread overview]
Message-ID: <176772367001.2054401.1990279895099735055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260106020738.466321-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 Tue, 6 Jan 2026 10:07:37 +0800 you wrote:
> Move WCN7850 workaround to the caller
>
> Changes v7
> - Update the if logic for firmware retrieval failure.
> - Link to v6:
> https://lore.kernel.org/all/20260105055646.3816296-1-shuai.zhang@oss.qualcomm.com/
> Changes v6
> - Add WCN7850 workaround details in the commit.
> - Reduce the logic nesting level.
> - Link to v5:
> https://lore.kernel.org/all/20251231075817.2611848-1-shuai.zhang@oss.qualcomm.com/
>
> [...]
Here is the summary with links:
- [v7,1/1] Bluetooth: btqca: move WCN7850 workaround to the caller
https://git.kernel.org/bluetooth/bluetooth-next/c/d6af4afb70c9
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-01-06 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 2:07 Shuai Zhang
2026-01-06 2:07 ` [PATCH v7 1/1] Bluetooth: btqca: move WCN7850 workaround to the caller Shuai Zhang
2026-01-06 2:17 ` Dmitry Baryshkov
2026-01-06 2:16 ` [PATCH v7 0/1] Bluetooth: btqca: move WCN7850 WA Dmitry Baryshkov
2026-01-06 2:21 ` Shuai Zhang
2026-01-06 2:32 ` Dmitry Baryshkov
2026-01-06 2:39 ` Shuai Zhang
2026-01-06 18:21 ` 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=176772367001.2054401.1990279895099735055.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®