From: "Gix, Brian" <brian.gix@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 1/2] mesh: Fix D-Bus node path
Date: Mon, 1 Jul 2019 16:34:03 +0000 [thread overview]
Message-ID: <1561998840.458.3.camel@intel.com> (raw)
In-Reply-To: <20190628082734.18809-1-michal.lowas-rzechonek@silvair.com>
Patch Applied
On Fri, 2019-06-28 at 10:27 +0200, Michał Lowas-Rzechonek wrote:
> According to doc/mesh-api.txt, node object should be located at
> /org/bluez/mesh/node.
> ---
> mesh/node.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mesh/node.c b/mesh/node.c
> index c2feaee52..45383b7d5 100644
> --- a/mesh/node.c
> +++ b/mesh/node.c
> @@ -47,7 +47,6 @@
> #define MIN_COMP_SIZE 14
>
> #define MESH_NODE_PATH_PREFIX "/node"
> -#define MESH_ELEMENT_PATH_PREFIX "/ele"
>
> /* Default values for a new locally created node */
> #define DEFAULT_NEW_UNICAST 0x0001
> @@ -1021,7 +1020,8 @@ static bool register_node_object(struct mesh_node *node)
> if (!hex2str(node->uuid, sizeof(node->uuid), uuid, sizeof(uuid)))
> return false;
>
> - node->path = l_strdup_printf(MESH_NODE_PATH_PREFIX "%s", uuid);
> + node->path = l_strdup_printf(BLUEZ_MESH_PATH MESH_NODE_PATH_PREFIX
> + "%s", uuid);
>
> if (!l_dbus_object_add_interface(dbus_get_bus(), node->path,
> MESH_NODE_INTERFACE, node))
prev parent reply other threads:[~2019-07-01 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:27 [PATCH BlueZ 1/2] mesh: Fix D-Bus node path Michał Lowas-Rzechonek
2019-06-28 8:27 ` [PATCH BlueZ 2/2] mesh: Register D-Bus management interface Michał Lowas-Rzechonek
2019-07-01 19:39 ` Michał Lowas-Rzechonek
2019-07-01 19:44 ` Gix, Brian
2019-07-01 6:07 ` [PATCH BlueZ 1/2] mesh: Fix D-Bus node path Stotland, Inga
2019-07-01 16:34 ` Gix, Brian [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=1561998840.458.3.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.com \
/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).