From: patchwork-bot+bluetooth@kernel.org
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, zijun_hu@icloud.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Zijun.Hu@oss.qualcomm.com
Subject: Re: [PATCH 0/2] Bluetooth: btusb: Sort WCN6855 device IDs and add one more ID
Date: Wed, 16 Jul 2025 19:00:06 +0000 [thread overview]
Message-ID: <175269240650.1291922.1087894854405140890.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715-q_newid-v1-0-8a1120c61fc9@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 15 Jul 2025 07:27:06 -0700 you wrote:
> This patch series is to:
> 1) Sort WCN6855 device IDs by VID and PID
> 2) Add one more WCN6855 device ID
>
> Signed-off-by: Zijun Hu <Zijun.Hu@oss.qualcomm.com>
> ---
> Zijun Hu (2):
> Bluetooth: btusb: Sort WCN6855 device IDs by VID and PID
> Bluetooth: btusb: Add one more ID 0x28de:0x1401 for Qualcomm WCN6855
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: btusb: Sort WCN6855 device IDs by VID and PID
https://git.kernel.org/bluetooth/bluetooth-next/c/108c86fadc41
- [2/2] Bluetooth: btusb: Add one more ID 0x28de:0x1401 for Qualcomm WCN6855
https://git.kernel.org/bluetooth/bluetooth-next/c/315fda1e9eb0
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-07-16 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 14:27 [PATCH 0/2] Bluetooth: btusb: Sort WCN6855 device IDs and add one more ID Zijun Hu
2025-07-15 14:27 ` [PATCH 1/2] Bluetooth: btusb: Sort WCN6855 device IDs by VID and PID Zijun Hu
2025-07-15 15:07 ` Bluetooth: btusb: Sort WCN6855 device IDs and add one more ID bluez.test.bot
2025-07-15 14:27 ` [PATCH 2/2] Bluetooth: btusb: Add one more ID 0x28de:0x1401 for Qualcomm WCN6855 Zijun Hu
2025-07-16 19:00 ` 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=175269240650.1291922.1087894854405140890.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=Zijun.Hu@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_zijuhu@quicinc.com \
--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