From: patchwork-bot+bluetooth@kernel.org
To: Shuai Zhang <quic_shuaz@quicinc.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_chejiang@quicinc.com,
quic_jiaymao@quicinc.com, quic_chezhou@quicinc.com
Subject: Re: [PATCH v3 0/1] Bluetooth: btusb: add new custom firmwares
Date: Mon, 10 Nov 2025 20:40:06 +0000 [thread overview]
Message-ID: <176280720699.2767842.6693108366892631498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251109092437.252022-1-quic_shuaz@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 9 Nov 2025 17:24:36 +0800 you wrote:
> add new custom firmwares
>
> Please refer to the link for information about the qcs2066 folder.
>
> a3f9f6dd047a ("Bluetooth: btusb: QCA: Support downloading custom-made firmwares")
>
> Changes for v3
> - remove CC stable
> - V2 link
> https://lore.kernel.org/all/20251107125405.1632663-1-quic_shuaz@quicinc.com/
>
> [...]
Here is the summary with links:
- [v3,1/1] Bluetooth: btusb: add new custom firmwares
https://git.kernel.org/bluetooth/bluetooth-next/c/c1b7e4ae360b
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-11-10 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 9:24 [PATCH v3 0/1] Bluetooth: btusb: add new custom firmwares Shuai Zhang
2025-11-09 9:24 ` [PATCH v3 1/1] " Shuai Zhang
2025-11-09 9:56 ` bluez.test.bot
2025-11-09 20:15 ` [PATCH v3 1/1] " Dmitry Baryshkov
2025-11-10 20:40 ` 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=176280720699.2767842.6693108366892631498.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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=quic_chejiang@quicinc.com \
--cc=quic_chezhou@quicinc.com \
--cc=quic_jiaymao@quicinc.com \
--cc=quic_shuaz@quicinc.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