From: patchwork-bot+bluetooth@kernel.org
To: Bastian Germann <bage@debian.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
johan.hedberg@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Bluetooth: btrtl: add support for the RTL8723CS
Date: Tue, 14 Mar 2023 23:10:20 +0000 [thread overview]
Message-ID: <167883542083.4543.5507901905040064892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230307221732.3391-1-bage@debian.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 7 Mar 2023 23:17:29 +0100 you wrote:
> Pinebook uses RTL8723CS for WiFi and bluetooth. Unfortunately, RTL8723CS
> has broken BT-4.1 support, so it requires a quirk.
>
> Add a quirk and wire up 8723CS support in btrtl.
> I was asked for a btmon output without the quirk;
> however, using the chip without the quirk ends up in a bad state with
> "Opcode 0x c77 failed: -56" (HCI_OP_READ_SYNC_TRAIN_PARAMS) on training.
> A btmon output with the quirk active was already sent by Vasily.
>
> [...]
Here is the summary with links:
- [v6,1/2] Bluetooth: Add new quirk for broken local ext features page 2
https://git.kernel.org/bluetooth/bluetooth-next/c/000b57d5c009
- [v6,2/2] Bluetooth: btrtl: add support for the RTL8723CS
https://git.kernel.org/bluetooth/bluetooth-next/c/b8e482d02513
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:[~2023-03-14 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 22:17 [PATCH v6 0/2] Bluetooth: btrtl: add support for the RTL8723CS Bastian Germann
2023-03-07 22:17 ` [PATCH v6 1/2] Bluetooth: Add new quirk for broken local ext features page 2 Bastian Germann
2023-03-07 22:59 ` Bluetooth: btrtl: add support for the RTL8723CS bluez.test.bot
2023-03-07 22:17 ` [PATCH v6 2/2] " Bastian Germann
2023-03-14 23: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=167883542083.4543.5507901905040064892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bage@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 \
/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.