From: Yao Zi <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] da772d: client/mgmt: Print UUID and flags when showing exp...
Date: Thu, 24 Jul 2025 13:40:17 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/cd1314-da772d@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: da772d62b295acbca12823c7e6e45534220f9c87
https://github.com/bluez/bluez/commit/da772d62b295acbca12823c7e6e45534220f9c87
Author: Yao Zi <ziyao@disroot.org>
Date: 2025-07-24 (Thu, 24 Jul 2025)
Changed paths:
M client/mgmt.c
Log Message:
-----------
client/mgmt: Print UUID and flags when showing experimental features
Command expinfo in mgmt menu queries experimental features from kernel
with MGMT_OP_READ_EXP_FEATURES_INFO. However, currently only the number
of experimental features are shown,
> expinfo
Global
Number of experimental features: 1
Primary controller (hci0)
Number of experimental features: 4
and lacking of details makes the command less useful. To ease debug,
this patch introduces extra output for the expinfo command, showing UUID
and flags of experimental features as well. A typical output will look
like,
> expinfo
Global
Number of experimental features: 1
6fbaf188-05e0-496a-9885-d6ddfdb4e03e (flags 0x0000)
Primary controller (hci0)
Number of experimental features: 4
671b10b5-42c0-4696-9227-eb28d1b049d6 (flags 0x0000)
330859bc-7506-492d-9370-9a6f0614037f (flags 0x0000)
6fbaf188-05e0-496a-9885-d6ddfdb4e03e (flags 0x0000)
2ce463d7-7a03-4d8d-bf05-5f24e8f36e76 (flags 0x0000)
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-24 20:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/cd1314-da772d@github.com \
--to=noreply@github.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 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.