From: patchwork-bot+bluetooth@kernel.org
To: Jiande Lu <jiande.lu@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, sean.wang@mediatek.com,
chris.lu@mediatek.com, deren.Wu@mediatek.com,
aaron.hou@mediatek.com, steve.lee@mediatek.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v5 1/2] Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925
Date: Wed, 24 Apr 2024 14:30:29 +0000 [thread overview]
Message-ID: <171396902901.2541.2890926466501511586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240423065157.21805-1-jiande.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 Tue, 23 Apr 2024 14:51:56 +0800 you wrote:
> Add HW IDs for wireless module specific to Acer/ASUS
> notebook models to ensure proper recognition and functionality.
> These HW IDs are extracted from Windows driver inf file.
> Note some HW IDs without official drivers, still in testing phase.
> Thus, we update module HW ID and test ensure consistent boot success.
>
> Signed-off-by: Jiande Lu <jiande.lu@mediatek.com>
>
> [...]
Here is the summary with links:
- [v5,1/2] Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925
https://git.kernel.org/bluetooth/bluetooth-next/c/3d513268312d
- [v5,2/2] Bluetooth: btusb: Sort usb_device_id table by the ID
https://git.kernel.org/bluetooth/bluetooth-next/c/2214b639ca14
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:[~2024-04-24 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 6:51 [PATCH v5 1/2] Bluetooth: btusb: Add USB HW IDs for MT7921/MT7922/MT7925 Jiande Lu
2024-04-23 6:51 ` [PATCH v5 2/2] Bluetooth: btusb: Sort usb_device_id table by the ID Jiande Lu
2024-04-24 14: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=171396902901.2541.2890926466501511586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aaron.hou@mediatek.com \
--cc=chris.lu@mediatek.com \
--cc=deren.Wu@mediatek.com \
--cc=jiande.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=steve.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).