linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v3 1/2] monitor: Add decoding support for LL Extended Feature Set
Date: Thu, 30 Oct 2025 22:30:06 +0000	[thread overview]
Message-ID: <176186340650.4061108.10347184025067875924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251030194856.296603-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, 30 Oct 2025 15:48:55 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This adds support for decoding LL Extended Feature Set introduced in 6.0
> that adds the following:
> 
> Commands:
> 
> [...]

Here is the summary with links:
  - [BlueZ,v3,1/2] monitor: Add decoding support for LL Extended Feature Set
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1479b279a016
  - [BlueZ,v3,2/2] monitor: Add decoding support for LL_FEATURE_EXT_{REQ,RSP}
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=32d740d87970

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-10-30 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 19:48 [PATCH BlueZ v3 1/2] monitor: Add decoding support for LL Extended Feature Set Luiz Augusto von Dentz
2025-10-30 19:48 ` [PATCH BlueZ v3 2/2] monitor: Add decoding support for LL_FEATURE_EXT_{REQ,RSP} Luiz Augusto von Dentz
2025-10-30 21:11 ` [BlueZ,v3,1/2] monitor: Add decoding support for LL Extended Feature Set bluez.test.bot
2025-10-30 22: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=176186340650.4061108.10347184025067875924.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).