From: "michal.lowas-rzechonek@silvair.com" <michal.lowas-rzechonek@silvair.com>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ v2 2/5] mesh: Validate application by comparing composition data
Date: Wed, 24 Jul 2019 09:55:11 +0200 [thread overview]
Message-ID: <20190724075511.elmqslt5kb3u3p2m@mlowasrzechonek2133> (raw)
In-Reply-To: <164c441cf7b43a1be420444676417f77f88a86c4.camel@intel.com>
Inga,
On 07/24, Stotland, Inga wrote:
> > - ele->path = l_strdup(path);
>
> The path needs to be preserved if this is the Attach() request.
> One way to do this would be to save it here, in the temporary node and
> then after all the checks are done, move it to the node that is "owned"
> by the daemon prior to deleting the temporary node in
> get_managed_objects_cb()
(...)
>
> So here, prior to removing the temorary node, the element paths need to
> be copied into the "req->attach" version of the node.
> Same goes for node->agent and node->provisioner.
True, thanks! I'll fix this in v3.
> "Location" property is described as optional in mesh-api.txt. It's
> populated with "Default Location", if the property is not present.
> I believe, it was more out of the convenience for the app develpers,
> but maybe we should change the property description as mandatory, i.e.,
> remove "optional" from the property descrition in mesh-api.txt
I'm inclined to make this property mandatory, but I don't have a strong
opinion about it. So just tell me how should it be and I'll adjust v3
accordingly.
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
next prev parent reply other threads:[~2019-07-24 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 10:06 [PATCH BlueZ v2 0/5] Use composition data to validate app against the node Michał Lowas-Rzechonek
2019-07-23 10:06 ` [PATCH BlueZ v2 1/5] mesh: Convert void pointers to anonymous unions in managed_obj_request Michał Lowas-Rzechonek
2019-07-23 10:06 ` [PATCH BlueZ v2 2/5] mesh: Validate application by comparing composition data Michał Lowas-Rzechonek
2019-07-24 4:30 ` Stotland, Inga
2019-07-24 7:55 ` michal.lowas-rzechonek [this message]
2019-07-24 18:09 ` Stotland, Inga
2019-07-24 19:12 ` michal.lowas-rzechonek
2019-07-24 21:24 ` Stotland, Inga
2019-07-23 10:06 ` [PATCH BlueZ v2 3/5] mesh: Keep element and model lists sorted and unique Michał Lowas-Rzechonek
2019-07-23 10:06 ` [PATCH BlueZ v2 4/5] mesh: Check that element indexes are consecutive Michał Lowas-Rzechonek
2019-07-23 10:06 ` [PATCH BlueZ v2 5/5] mesh: Check that config server is present in primary element Michał Lowas-Rzechonek
2019-07-24 4:38 ` [PATCH BlueZ v2 0/5] Use composition data to validate app against the node Stotland, Inga
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=20190724075511.elmqslt5kb3u3p2m@mlowasrzechonek2133 \
--to=michal.lowas-rzechonek@silvair.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 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).