All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Valentin David <valentin.david@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btusb: Add device 0489:e0f5 as MT7922 device
Date: Thu, 06 Jul 2023 20:10:10 +0000	[thread overview]
Message-ID: <168867421010.27620.7433022824880919772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230706191035.736632-1-valentin.david@gmail.com>

Hello:

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

On Thu,  6 Jul 2023 21:10:18 +0200 you wrote:
> Asus ROG Ally gaming computer has a MediaTek MT7922 chip that uses USB id
> 0489:e0f5 and needs to be added to the table. Without this, the device is
> not usable and gives the following error:
> 
> Bluetooth: hci0: Opcode 0x c03 failed: -110
> 
> Output from /sys/kernel/debug/usb/devices:
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btusb: Add device 0489:e0f5 as MT7922 device
    https://git.kernel.org/bluetooth/bluetooth-next/c/65f2a9a7d004

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



      parent reply	other threads:[~2023-07-06 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 21:01 [PATCH] Bluetooth: btusb: Add device 0489:e0f5 as MT7922 device Valentin David
2023-07-02 21:32 ` bluez.test.bot
2023-07-05 23:00 ` [PATCH] " patchwork-bot+bluetooth
2023-07-06 19:10 ` [PATCH v2] " Valentin David
2023-07-06 19:12   ` [v2] " bluez.test.bot
2023-07-06 19:17   ` [PATCH v2] " Valentin David
2023-07-06 20: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=168867421010.27620.7433022824880919772.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=valentin.david@gmail.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 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.