All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Tibor Harcsa <silurust@gmail.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table
Date: Tue, 30 Jun 2026 20:32:36 +0000	[thread overview]
Message-ID: <178285155638.267316.9485052012945402309.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260629203420.24137-1-silurust@gmail.com>

Hello:

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

On Mon, 29 Jun 2026 22:34:20 +0200 you wrote:
> Add the USB ID (13d3:3503) for the IMC Networks Qualcomm Atheros
> QCA9377 Bluetooth controller to the btusb quirks table. This device
> requires Qualcomm Rome firmware and wideband speech support to function
> properly; otherwise, BLE scanning fails with HCI unexpected event
> opcode 0x2005 errors.
> 
> The device reports the following in /sys/kernel/debug/usb/devices:
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table
    https://git.kernel.org/bluetooth/bluetooth-next/c/547fc6a4a51a

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



      parent reply	other threads:[~2026-06-30 20:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 15:35 [PATCH] Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table Tibor Harcsa
2026-06-29 17:56 ` Luiz Augusto von Dentz
     [not found]   ` <CAN2GrM=0wVS03c3zoCwWAJTXrUkRiUhtyJfqprMAhwTKUGzOeQ@mail.gmail.com>
2026-06-29 19:07     ` Luiz Augusto von Dentz
2026-06-29 19:08     ` Tibor Harcsa
2026-06-29 19:53 ` [PATCH v2] " Tibor Harcsa
2026-06-29 20:32   ` [v2] " bluez.test.bot
2026-06-29 20:34 ` [PATCH v2] " Tibor Harcsa
2026-06-29 21:57   ` [v2] " bluez.test.bot
2026-06-30 20:32   ` 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=178285155638.267316.9485052012945402309.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=silurust@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.