All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?6Z2S5Y+2IOilv+WfjiA8c3VubGl3ZWkyMDE1c0BvdXRsb29rLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922
Date: Thu, 15 May 2025 17:10:30 +0000	[thread overview]
Message-ID: <174732903051.3181810.414853071879946435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <SY7P300MB0829AE8C53A9A35F9038F97ABF832@SY7P300MB0829.AUSP300.PROD.OUTLOOK.COM>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 30 Apr 2025 23:50:50 +0000 you wrote:
> From dcb763edda3fd9f3fdb6525b07072fdd136d713a Mon Sep 17 00:00:00 2001
> From: Liwei Sun <sunliwei2015s@outlook.com>
> Date: Thu, 1 May 2025 06:18:50 +0800
> Subject: [PATCH] Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922
> 
> A new variant of MT7922 wireless device has been identified.
> The device introduces itself as MEDIATEK MT7922,
> so treat it as MediaTek device.
> With this patch, btusb driver works as expected:
> [    3.151162] Bluetooth: Core ver 2.22
> [    3.151185] Bluetooth: HCI device and connection manager initialized
> [    3.151189] Bluetooth: HCI socket layer initialized
> [    3.151191] Bluetooth: L2CAP socket layer initialized
> [    3.151194] Bluetooth: SCO socket layer initialized
> [    3.295718] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20241106163512
> [    4.676634] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [    4.676637] Bluetooth: BNEP filters: protocol multicast
> [    4.676640] Bluetooth: BNEP socket layer initialized
> [    5.560453] Bluetooth: hci0: Device setup in 2320660 usecs
> [    5.560457] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
> [    5.619197] Bluetooth: hci0: AOSP extensions version v1.00
> [    5.619204] Bluetooth: hci0: AOSP quality report is supported
> [    5.619301] Bluetooth: MGMT ver 1.23
> [    6.741247] Bluetooth: RFCOMM TTY layer initialized
> [    6.741258] Bluetooth: RFCOMM socket layer initialized
> [    6.741261] Bluetooth: RFCOMM ver 1.11
> 
> [...]

Here is the summary with links:
  - Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922
    https://git.kernel.org/bluetooth/bluetooth-next/c/72d82f47a019

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-05-15 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 23:50 [PATCH] Bluetooth: btusb: Add new VID/PID 13d3/3584 for MT7922 青叶 西城
2025-05-01  1:14 ` bluez.test.bot
2025-05-15 17:10 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-12  2:31 [PATCH] " Liwei Sun
2025-05-12 21:37 ` Luiz Augusto von Dentz
2025-05-13  6:13 Liwei Sun
2025-05-15 17:10 ` patchwork-bot+bluetooth

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=174732903051.3181810.414853071879946435.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?6Z2S5Y+2IOilv+WfjiA8c3VubGl3ZWkyMDE1c0BvdXRsb29rLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.