From: patchwork-bot+bluetooth@kernel.org
To: Chris Lu <chris.lu@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, sean.wang@mediatek.com,
will-cy.Lee@mediatek.com, ss.wu@mediatek.com,
steve.lee@mediatek.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 RESEND 0/2] Add two new ID for MediaTek's Bluetooth
Date: Wed, 22 Oct 2025 13:50:10 +0000 [thread overview]
Message-ID: <176114101049.1909224.7135864082942324713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251015033150.498866-1-chris.lu@mediatek.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 Oct 2025 11:31:48 +0800 you wrote:
> In response to the customer's request, add the following two
> VID/PID to the USB driver table so that btusb driver can support
> the corresponding MT7920/MT7922 modules.
>
> 1. VID/PID 0489/e135 for MT7920
> 2. VID/PID 0489/e170 for MT7922
>
> [...]
Here is the summary with links:
- [v2,RESEND,1/2] Bluetooth: btusb: MT7920: Add VID/PID 0489/e135
https://git.kernel.org/bluetooth/bluetooth-next/c/bb9da27b29d0
- [v2,RESEND,2/2] Bluetooth: btusb: MT7922: Add VID/PID 0489/e170
https://git.kernel.org/bluetooth/bluetooth-next/c/042b9b4c55c7
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-10-22 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 3:31 Chris Lu
2025-10-15 3:31 ` [PATCH v2 RESEND 1/2] Bluetooth: btusb: MT7920: Add VID/PID 0489/e135 Chris Lu
2025-10-16 14:51 ` Paul Menzel
2025-10-15 3:31 ` [PATCH v2 RESEND 2/2] Bluetooth: btusb: MT7922: Add VID/PID 0489/e170 Chris Lu
2025-10-16 15:10 ` Paul Menzel
2025-10-22 13:50 ` 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=176114101049.1909224.7135864082942324713.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chris.lu@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
--cc=ss.wu@mediatek.com \
--cc=steve.lee@mediatek.com \
--cc=will-cy.Lee@mediatek.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®