From: patchwork-bot+bluetooth@kernel.org
To: Max Chou <max.chou@realtek.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
hildawu@realtek.com, alex_lu@realsil.com.cn,
niall_ni@realsil.com.cn, kidman@realtek.com
Subject: Re: [PATCH 0/3] Bluetooth: btusb: Add new VID/PID for RTL8852BE-VT
Date: Fri, 07 Nov 2025 19:10:10 +0000 [thread overview]
Message-ID: <176254261098.1132280.13623781765700879277.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105055041.456142-1-max.chou@realtek.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 5 Nov 2025 13:50:38 +0800 you wrote:
> This patch series adds new VID/PID support for RTL8852BE-VT.
>
> Max Chou (3):
> Bluetooth: btusb: Add new VID/PID 0x0489/0xE12F for RTL8852BE-VT
> Bluetooth: btusb: Add new VID/PID 0x13d3/0x3618 for RTL8852BE-VT
> Bluetooth: btusb: Add new VID/PID 0x13d3/0x3619 for RTL8852BE-VT
>
> [...]
Here is the summary with links:
- [1/3] Bluetooth: btusb: Add new VID/PID 0x0489/0xE12F for RTL8852BE-VT
https://git.kernel.org/bluetooth/bluetooth-next/c/234c42bfac07
- [2/3] Bluetooth: btusb: Add new VID/PID 0x13d3/0x3618 for RTL8852BE-VT
https://git.kernel.org/bluetooth/bluetooth-next/c/121a21fd7599
- [3/3] Bluetooth: btusb: Add new VID/PID 0x13d3/0x3619 for RTL8852BE-VT
https://git.kernel.org/bluetooth/bluetooth-next/c/92f51644e1cf
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-07 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 5:50 Max Chou
2025-11-05 5:50 ` [PATCH 1/3] Bluetooth: btusb: Add new VID/PID 0x0489/0xE12F " Max Chou
2025-11-05 5:50 ` [PATCH 2/3] Bluetooth: btusb: Add new VID/PID 0x13d3/0x3618 " Max Chou
2025-11-05 5:50 ` [PATCH 3/3] Bluetooth: btusb: Add new VID/PID 0x13d3/0x3619 " Max Chou
2025-11-07 19:10 ` 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=176254261098.1132280.13623781765700879277.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex_lu@realsil.com.cn \
--cc=hildawu@realtek.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=niall_ni@realsil.com.cn \
/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®