From: "Frédéric Danis" <frederic.danis@collabora.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v4 6/6] client: Display SecurityLevel in device info
Date: Tue, 29 Sep 2026 12:19:53 +0200 [thread overview]
Message-ID: <20260929101953.254969-7-frederic.danis@collabora.com> (raw)
In-Reply-To: <20260929101953.254969-1-frederic.danis@collabora.com>
---
client/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/client/main.c b/client/main.c
index 314aead8c..8298fc9eb 100644
--- a/client/main.c
+++ b/client/main.c
@@ -2020,6 +2020,8 @@ static void cmd_info(int argc, char *argv[])
print_property(proxy, "WakeAllowed");
print_property(proxy, "LegacyPairing");
print_property(proxy, "CablePairing");
+ print_property(proxy, "SecurityLevel");
+ print_property(proxy, "EncryptionType");
print_uuids(proxy);
print_property(proxy, "Modalias");
print_property(proxy, "ManufacturerData");
--
2.43.0
next prev parent reply other threads:[~2026-09-29 10:20 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 ` Frédéric Danis [this message]
2026-10-01 17:40 ` [PATCH BlueZ v4 0/6] mgmt/device: report link security level to D-Bus clients patchwork-bot+bluetooth
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=20260929101953.254969-7-frederic.danis@collabora.com \
--to=frederic.danis@collabora.com \
--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 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).