From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v6 6/6] adapter: Remove experimental flag for PowerState
Date: Thu, 1 Sep 2022 12:43:31 +0200 [thread overview]
Message-ID: <20220901104331.174588-6-hadess@hadess.net> (raw)
In-Reply-To: <20220901104331.174588-1-hadess@hadess.net>
Now that the feature has been tested, that the API is deemed adequate
and the reliability sufficient.
---
src/adapter.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/adapter.c b/src/adapter.c
index dc96b9718..b3d25f4b0 100644
--- a/src/adapter.c
+++ b/src/adapter.c
@@ -3861,8 +3861,7 @@ static const GDBusPropertyTable adapter_properties[] = {
{ "Alias", "s", property_get_alias, property_set_alias },
{ "Class", "u", property_get_class },
{ "Powered", "b", property_get_powered, property_set_powered },
- { "PowerState", "s", property_get_power_state, NULL, NULL,
- G_DBUS_PROPERTY_FLAG_EXPERIMENTAL },
+ { "PowerState", "s", property_get_power_state },
{ "Discoverable", "b", property_get_discoverable,
property_set_discoverable },
{ "DiscoverableTimeout", "u", property_get_discoverable_timeout,
--
2.37.2
next prev parent reply other threads:[~2022-09-01 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:43 [PATCH BlueZ v6 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 2/6] adapter: Implement PowerState property Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 3/6] client: Print the " Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 5/6] adapter: Fix typo in function name Bastien Nocera
2022-09-01 10:43 ` Bastien Nocera [this message]
2022-09-01 11:07 ` [PATCH BlueZ v6 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-09-01 11:32 ` [BlueZ,v6,1/6] " bluez.test.bot
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=20220901104331.174588-6-hadess@hadess.net \
--to=hadess@hadess.net \
--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