All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v4 0/6] mgmt/device: report link security level to D-Bus clients
Date: Thu, 01 Oct 2026 17:40:16 +0000	[thread overview]
Message-ID: <179087641603.3027576.11599397534070933900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929101953.254969-1-frederic.danis@collabora.com>

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 29 Sep 2026 12:19:47 +0200 you wrote:
> This series adds connection security-level reporting.
> The new MGMT_EV_SECURITY_LEVEL_CHANGED event [1] is documented and
> org.bluez.Device1 is updates with new experimental read-only properties
> SecurityLevel and EncryptionType.
> Those properties can be displayed using "bluetoothctl info".
> 
> This is intended to let clients (including test tooling such as btpclient)
> observe effective link security changes.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v4,1/6] mgmt: Add Security Level Changed event
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bb98c3e02282
  - [BlueZ,v4,2/6] mgmt-tester: Add Security Level Changed event tests
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=74334ac97049
  - [BlueZ,v4,3/6] monitor: Add support for Mgmt Security Level changed event
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1391af1995a9
  - [BlueZ,v4,4/6] device: Add SecurityLevel properties to org.bluez.Device1
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=09e58eb8da1b
  - [BlueZ,v4,5/6] org.bluez.Device: Add Security Level related properties
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d3f2b6f3e142
  - [BlueZ,v4,6/6] client: Display SecurityLevel in device info
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ae69dcddd549

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



      parent reply	other threads:[~2026-10-01 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 10:19 [PATCH BlueZ v4 0/6] mgmt/device: report link security level to D-Bus clients Frédéric Danis
2026-09-29 10:19 ` [PATCH BlueZ v4 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-09-29 14:42   ` mgmt/device: report link security level to D-Bus clients bluez.test.bot
2026-09-29 10:19 ` [PATCH BlueZ v4 2/6] mgmt-tester: Add Security Level Changed event tests Frédéric Danis
2026-09-29 10:19 ` [PATCH BlueZ v4 3/6] monitor: Add support for Mgmt Security Level changed event Frédéric Danis
2026-09-29 10:19 ` [PATCH BlueZ v4 4/6] device: Add SecurityLevel properties to org.bluez.Device1 Frédéric Danis
2026-09-29 10:19 ` [PATCH BlueZ v4 5/6] org.bluez.Device: Add Security Level related properties Frédéric Danis
2026-09-29 10:19 ` [PATCH BlueZ v4 6/6] client: Display SecurityLevel in device info Frédéric Danis
2026-10-01 17:40 ` 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=179087641603.3027576.11599397534070933900.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.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 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.