From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 1/1] mesh: Set node ID for a newly provisioned node
Date: Mon, 11 Mar 2019 22:19:46 +0000 [thread overview]
Message-ID: <1552342784.29289.1.camel@intel.com> (raw)
In-Reply-To: <20190308225634.20351-1-inga.stotland@intel.com>
Applied
On Fri, 2019-03-08 at 14:56 -0800, Inga Stotland wrote:
> When a new node is created after successful provisioning, a 4-digit
> hex node id needs to be generated and preserved.
> ---
> mesh/storage.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mesh/storage.c b/mesh/storage.c
> index fe3102fba..e84c2c933 100644
> --- a/mesh/storage.c
> +++ b/mesh/storage.c
> @@ -546,6 +546,8 @@ bool storage_create_node_config(struct mesh_node *node, void *data)
> if (num_tries == 10)
> l_error("Failed to generate unique node ID");
>
> + node_id_set(node, node_id);
> +
> snprintf(name_buf, PATH_MAX, "%s/%04x", storage_dir, node_id);
>
> /* Create a new directory and node.json file */
prev parent reply other threads:[~2019-03-11 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 22:56 [PATCH BlueZ 1/1] mesh: Set node ID for a newly provisioned node Inga Stotland
2019-03-11 22:19 ` 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=1552342784.29289.1.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.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.