From: patchwork-bot+bluetooth@kernel.org
To: Archie Pusaka <apusaka@google.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
johan.hedberg@gmail.com, marcel@holtmann.org,
chromeos-bluetooth-upstreaming@chromium.org,
apusaka@chromium.org, abhishekpandit@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: Populate hci_set_hw_info for Intel and Realtek
Date: Wed, 24 Apr 2024 14:20:29 +0000 [thread overview]
Message-ID: <171396842922.29186.2152578622770434073.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240422172027.v2.1.Ib96985e197f3db620a127a84aa20f3f3017aaf57@changeid>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 22 Apr 2024 17:20:28 +0800 you wrote:
> From: Archie Pusaka <apusaka@chromium.org>
>
> The hardware information surfaced via debugfs might be usable by the
> userspace to set some configuration knobs. This patch sets the hw_info
> for Intel and Realtek chipsets.
>
> Below are some possible output of the hardware_info debugfs file.
> INTEL platform=55 variant=24
> RTL lmp_subver=34898 hci_rev=10 hci_ver=11 hci_bus=1
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Populate hci_set_hw_info for Intel and Realtek
https://git.kernel.org/bluetooth/bluetooth-next/c/46d8da86787b
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:[~2024-04-24 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 9:20 [PATCH v2] Bluetooth: Populate hci_set_hw_info for Intel and Realtek Archie Pusaka
2024-04-22 9:57 ` [v2] " bluez.test.bot
2024-04-24 14: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=171396842922.29186.2152578622770434073.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@google.com \
--cc=apusaka@chromium.org \
--cc=apusaka@google.com \
--cc=chromeos-bluetooth-upstreaming@chromium.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 \
/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