From: patchwork-bot+bluetooth@kernel.org
To: Sean Wang <sean.wang@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
ulf.hansson@linaro.org, linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-mmc@vger.kernel.org,
sean.wang@mediatek.com
Subject: Re: [PATCH v2 1/8] mmc: sdio: add MediaTek MT7902 SDIO device ID
Date: Tue, 24 Feb 2026 20:30:07 +0000 [thread overview]
Message-ID: <177196500778.4139022.732715685642852259.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260224061325.20189-1-sean.wang@kernel.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 24 Feb 2026 00:13:18 -0600 you wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Add SDIO device ID (0x790a) for MediaTek MT7902 to sdio_ids.h.
>
> Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>
> [...]
Here is the summary with links:
- [v2,1/8] mmc: sdio: add MediaTek MT7902 SDIO device ID
https://git.kernel.org/bluetooth/bluetooth-next/c/30c211ed0440
- [v2,2/8] Bluetooth: btmtk: add MT7902 MCU support
https://git.kernel.org/bluetooth/bluetooth-next/c/ad7c85c44e42
- [v2,3/8] Bluetooth: btusb: Add new VID/PID 13d3/3579 for MT7902
https://git.kernel.org/bluetooth/bluetooth-next/c/39b32232e047
- [v2,4/8] Bluetooth: btusb: Add new VID/PID 13d3/3580 for MT7902
https://git.kernel.org/bluetooth/bluetooth-next/c/cde58a6f8d84
- [v2,5/8] Bluetooth: btusb: Add new VID/PID 13d3/3594 for MT7902
https://git.kernel.org/bluetooth/bluetooth-next/c/71fa9af03199
- [v2,6/8] Bluetooth: btusb: Add new VID/PID 13d3/3596 for MT7902
https://git.kernel.org/bluetooth/bluetooth-next/c/2dbd6783e368
- [v2,7/8] Bluetooth: btusb: Add new VID/PID 0e8d/1ede for MT7902
https://git.kernel.org/bluetooth/bluetooth-next/c/df6be153d1bb
- [v2,8/8] Bluetooth: btmtk: add MT7902 SDIO support
https://git.kernel.org/bluetooth/bluetooth-next/c/287f90321f25
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:[~2026-02-24 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 6:13 [PATCH v2 1/8] mmc: sdio: add MediaTek MT7902 SDIO device ID Sean Wang
2026-02-24 6:13 ` [PATCH v2 2/8] Bluetooth: btmtk: add MT7902 MCU support Sean Wang
2026-02-24 6:13 ` [PATCH v2 3/8] Bluetooth: btusb: Add new VID/PID 13d3/3579 for MT7902 Sean Wang
2026-02-24 6:13 ` [PATCH v2 4/8] Bluetooth: btusb: Add new VID/PID 13d3/3580 " Sean Wang
2026-02-24 6:13 ` [PATCH v2 5/8] Bluetooth: btusb: Add new VID/PID 13d3/3594 " Sean Wang
2026-02-24 6:13 ` [PATCH v2 6/8] Bluetooth: btusb: Add new VID/PID 13d3/3596 " Sean Wang
2026-02-24 6:13 ` [PATCH v2 7/8] Bluetooth: btusb: Add new VID/PID 0e8d/1ede " Sean Wang
2026-02-24 6:13 ` [PATCH v2 8/8] Bluetooth: btmtk: add MT7902 SDIO support Sean Wang
2026-02-24 20:30 ` 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=177196500778.4139022.732715685642852259.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=ulf.hansson@linaro.org \
/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