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 features bits defined in 6.2
Date: Wed, 06 May 2026 13:30:11 +0000 [thread overview]
Message-ID: <177807421130.2587487.11389095373099968743.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260504211303.1081876-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 Mon, 4 May 2026 17:13:01 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds features bits defined as per core spec 6.2:
> https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/low-energy-controller/link-layer-specification.html#UUID-56ada5ed-4ae3-acee-198f-27ead57d86f1
> ---
> monitor/packet.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Here is the summary with links:
- [BlueZ,v1,1/2] monitor: Add features bits defined in 6.2
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fda84f7004fa
- [BlueZ,v1,2/2] monitor: Add decoding for Short Connection Interval feature
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=79cfd07224ff
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:[~2026-05-06 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 21:13 [PATCH BlueZ v1 1/2] monitor: Add features bits defined in 6.2 Luiz Augusto von Dentz
2026-05-04 21:13 ` [PATCH BlueZ v1 2/2] monitor: Add decoding for Short Connection Interval feature Luiz Augusto von Dentz
2026-05-04 22:42 ` [BlueZ,v1,1/2] monitor: Add features bits defined in 6.2 bluez.test.bot
2026-05-06 13:30 ` 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=177807421130.2587487.11389095373099968743.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