From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/2] monitor: Add page information to print_features_subpage
Date: Fri, 14 Nov 2025 17:12:06 +0000 [thread overview]
Message-ID: <176314032674.1740925.17555659694388224656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113155818.2628720-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 13 Nov 2025 10:58:17 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This makes print_features_subpage print the page they belong:
>
> > HCI Event: Command Complete (0x0e) plen 253
> LE Read All Local Features (0x08|0x0087) ncmd 1
> Status: Success (0x00)
> Page: 10
> Features[0/0][8]: 403900f301000080
> LL Privacy
> LE 2M PHY
> LE Coded PHY
> LE Extended Advertising
> LE Periodic Advertising
> Periodic Advertising Sync Transfer - Sender
> Periodic Advertising Sync Transfer - Recipient
> Connected Isochronous Stream - Central
> Connected Isochronous Stream - Peripheral
> Isochronous Broadcaster
> Synchronized Receiver
> Connected Isochronous Stream (Host Support)
> LL Extended Feature Set
> Features[1/0][8]: 0000000000000000
> Features[1/1][8]: 0000000000000000
> Features[1/2][8]: 0000000000000000
> Features[2/0][8]: 0000000000000000
> Features[2/1][8]: 0000000000000000
> Features[2/2][8]: 0000000000000000
> Features[3/0][8]: 0000000000000000
> Features[3/1][8]: 0000000000000000
> Features[3/2][8]: 0000000000000000
> Features[4/0][8]: 0000000000000000
> Features[4/1][8]: 0000000000000000
> Features[4/2][8]: 0000000000000000
> Features[5/0][8]: 0000000000000000
> Features[5/1][8]: 0000000000000000
> Features[5/2][8]: 0000000000000000
> Features[6/0][8]: 0000000000000000
> Features[6/1][8]: 0000000000000000
> Features[6/2][8]: 0000000000000000
> Features[7/0][8]: 0000000000000000
> Features[7/1][8]: 0000000000000000
> Features[7/2][8]: 0000000000000000
> Features[8/0][8]: 0000000000000000
> Features[8/1][8]: 0000000000000000
> Features[8/2][8]: 0000000000000000
> Features[9/0][8]: 0000000000000000
> Features[9/1][8]: 0000000000000000
> Features[9/2][8]: 0000000000000000
> Features[10/0][8]: 0000000000000000
> Features[10/1][8]: 0000000000000000
> Features[10/2][8]: 0000000000000000
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/2] monitor: Add page information to print_features_subpage
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f67b72b4cc39
- [BlueZ,v1,2/2] btdev: Fix set_bredrle_commands
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4bf47f880d06
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-11-14 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:58 [PATCH BlueZ v1 1/2] monitor: Add page information to print_features_subpage Luiz Augusto von Dentz
2025-11-13 15:58 ` [PATCH BlueZ v1 2/2] btdev: Fix set_bredrle_commands Luiz Augusto von Dentz
2025-11-13 17:31 ` [BlueZ,v1,1/2] monitor: Add page information to print_features_subpage bluez.test.bot
2025-11-14 17:12 ` 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=176314032674.1740925.17555659694388224656.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).