From: patchwork-bot+bluetooth@kernel.org
To: Hsin-chen Chuang <chharry@google.com>
Cc: luiz.dentz@gmail.com, chharry@chromium.org,
chromeos-bluetooth-upstreaming@chromium.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, johan.hedberg@gmail.com,
marcel@holtmann.org, pabeni@redhat.com, horms@kernel.org,
yinghsu@chromium.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/4] Bluetooth: Introduce HCI Driver protocol
Date: Wed, 16 Apr 2025 16:20:32 +0000 [thread overview]
Message-ID: <174482043201.3420647.14476412419394286176.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250416095505.769906-1-chharry@google.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 16 Apr 2025 09:53:35 +0000 you wrote:
> From: Hsin-chen Chuang <chharry@chromium.org>
>
> Although commit 75ddcd5ad40e ("Bluetooth: btusb: Configure altsetting
> for HCI_USER_CHANNEL") has enabled the HCI_USER_CHANNEL user to send out
> SCO data through USB Bluetooth chips, it's observed that with the patch
> HFP is flaky on most of the existing USB Bluetooth controllers: Intel
> chips sometimes send out no packet for Transparent codec; MTK chips may
> generate SCO data with a wrong handle for CVSD codec; RTK could split
> the data with a wrong packet size for Transparent codec; ... etc.
>
> [...]
Here is the summary with links:
- [v2,1/4] Bluetooth: Introduce HCI Driver protocol
(no matching commit)
- [v2,2/4] Bluetooth: btusb: Add HCI Drv commands for configuring altsetting
(no matching commit)
- [v2,3/4] Revert "Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL"
https://git.kernel.org/bluetooth/bluetooth-next/c/3947fa617367
- [v2,4/4] Revert "Bluetooth: btusb: add sysfs attribute to control USB alt setting"
https://git.kernel.org/bluetooth/bluetooth-next/c/79f21135b7b0
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:[~2025-04-16 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 9:53 [PATCH v2 1/4] Bluetooth: Introduce HCI Driver protocol Hsin-chen Chuang
2025-04-16 9:53 ` [PATCH v2 2/4] Bluetooth: btusb: Add HCI Drv commands for configuring altsetting Hsin-chen Chuang
2025-04-16 9:53 ` [PATCH v2 3/4] Revert "Bluetooth: btusb: Configure altsetting for HCI_USER_CHANNEL" Hsin-chen Chuang
2025-04-16 9:53 ` [PATCH v2 4/4] Revert "Bluetooth: btusb: add sysfs attribute to control USB alt setting" Hsin-chen Chuang
2025-04-16 10:36 ` [v2,1/4] Bluetooth: Introduce HCI Driver protocol bluez.test.bot
2025-04-16 16:20 ` 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=174482043201.3420647.14476412419394286176.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chharry@chromium.org \
--cc=chharry@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yinghsu@chromium.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