From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <zijun_hu@icloud.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, steev@kali.org,
bjorande@quicinc.com, quic_aiquny@quicinc.com,
quic_chejiang@quicinc.com, johan@kernel.org,
jens.glathe@oldschoolsolutions.biz, pmenzel@molgen.mpg.de,
luiz.von.dentz@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_zijuhu@quicinc.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: qca: Fix poor RF performance for WCN6855
Date: Tue, 14 Jan 2025 17:20:36 +0000 [thread overview]
Message-ID: <173687523651.62266.7168479061326166895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250113-wcn6855_fix-v3-1-eeb8b0e19ef4@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 13 Jan 2025 22:43:23 +0800 you wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
>
> For WCN6855, board ID specific NVM needs to be downloaded once board ID
> is available, but the default NVM is always downloaded currently.
>
> The wrong NVM causes poor RF performance, and effects user experience
> for several types of laptop with WCN6855 on the market.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: qca: Fix poor RF performance for WCN6855
https://git.kernel.org/bluetooth/bluetooth-next/c/67f8711aae4b
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:[~2025-01-14 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 14:43 [PATCH v3] Bluetooth: qca: Fix poor RF performance for WCN6855 Zijun Hu
2025-01-13 15:04 ` Johan Hovold
2025-01-13 15:11 ` Zijun Hu
2025-01-13 15:17 ` Johan Hovold
2025-01-13 15:15 ` Zijun Hu
2025-01-13 15:22 ` Johan Hovold
2025-01-14 4:10 ` Steev Klimaszewski
2025-01-14 17: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=173687523651.62266.7168479061326166895.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bjorande@quicinc.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_aiquny@quicinc.com \
--cc=quic_chejiang@quicinc.com \
--cc=quic_zijuhu@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=steev@kali.org \
--cc=zijun_hu@icloud.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