From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC BlueZ 1/2] mesh: Rename IVUpdate import flag to IvUpdate
Date: Thu, 9 Jan 2020 09:38:54 +0100 [thread overview]
Message-ID: <20200109083855.16000-2-michal.lowas-rzechonek@silvair.com> (raw)
In-Reply-To: <20200109083855.16000-1-michal.lowas-rzechonek@silvair.com>
Name change for consistency with "IvIndex" property.
---
doc/mesh-api.txt | 2 +-
mesh/mesh.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 6f9531019..b33c24e12 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -188,7 +188,7 @@ Methods:
The flags parameter is a dictionary containing provisioning
flags. Supported values are:
- boolean IVUpdate
+ boolean IvUpdate
When true, indicates that the network is in the
middle of IV Index Update procedure.
diff --git a/mesh/mesh.c b/mesh/mesh.c
index 6d2f86b6d..972beecc9 100644
--- a/mesh/mesh.c
+++ b/mesh/mesh.c
@@ -777,7 +777,7 @@ static struct l_dbus_message *import_call(struct l_dbus *dbus,
"Bad net index");
while (l_dbus_message_iter_next_entry(&iter_flags, &key, &var)) {
- if (!strcmp(key, "IVUpdate")) {
+ if (!strcmp(key, "IvUpdate")) {
if (!l_dbus_message_iter_get_variant(&var, "b",
&ivu))
goto fail;
--
2.19.1
next prev parent reply other threads:[~2020-01-09 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 8:38 [RFC BlueZ 0/2] Fix types and names of beacon/import flags Michał Lowas-Rzechonek
2020-01-09 8:38 ` Michał Lowas-Rzechonek [this message]
2020-01-09 8:38 ` [RFC BlueZ 2/2] mesh: Change BeaconFlags property type to a dict Michał Lowas-Rzechonek
2020-01-21 20:15 ` [RFC BlueZ 0/2] Fix types and names of beacon/import flags Michał Lowas-Rzechonek
2020-01-22 0:44 ` Stotland, Inga
2020-01-22 1:14 ` Gix, Brian
2020-01-22 17:13 ` michal.lowas-rzechonek
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=20200109083855.16000-2-michal.lowas-rzechonek@silvair.com \
--to=michal.lowas-rzechonek@silvair.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).