From: patchwork-bot+bluetooth@kernel.org
To: Pedro Nishiyama <nishiyama.pedro@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, johan.hedberg@gmail.com
Subject: Re: [PATCH v2 1/2] Bluetooth: Add new quirks for fake Bluetooth dongles
Date: Tue, 04 Mar 2025 15:00:31 +0000 [thread overview]
Message-ID: <174110043148.174904.12856753542973603477.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250222050439.1494-1-nishiyama.pedro@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 22 Feb 2025 02:04:38 -0300 you wrote:
> This adds quirks for broken READ_VOICE_SETTING and READ_PAGE_SCAN_TYPE.
>
> Signed-off-by: Pedro Nishiyama <nishiyama.pedro@gmail.com>
> ---
> include/net/bluetooth/hci.h | 16 ++++++++++++++++
> net/bluetooth/hci_sync.c | 6 ++++++
> 2 files changed, 22 insertions(+)
Here is the summary with links:
- [v2,1/2] Bluetooth: Add new quirks for fake Bluetooth dongles
(no matching commit)
- [v2,2/2] Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers
https://git.kernel.org/bluetooth/bluetooth-next/c/c2fe96fc96f7
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-03-04 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 5:04 [PATCH v2 1/2] Bluetooth: Add new quirks for fake Bluetooth dongles Pedro Nishiyama
2025-02-22 5:04 ` [PATCH v2 2/2] Bluetooth: btusb: Fix regression in the initialization of fake Bluetooth controllers Pedro Nishiyama
2025-02-22 5:29 ` Paul Menzel
2025-02-22 6:35 ` Pedro Nishiyama
2025-02-24 21:56 ` Paul Menzel
2025-02-22 5:26 ` [PATCH v2 1/2] Bluetooth: Add new quirks for fake Bluetooth dongles Paul Menzel
2025-02-22 5:31 ` [v2,1/2] " bluez.test.bot
2025-03-04 15:00 ` 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=174110043148.174904.12856753542973603477.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=nishiyama.pedro@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.