Re: [PATCH BlueZ v6 0/5] Use composition data to validate app against the

["Stotland, Inga" <inga.stotland@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

Hi Michal,

On Fri, 2019-07-26 at 08:36 +0200, Michał Lowas-Rzechonek wrote:
> Thanks for your patience :)
> 
> + Fix brace style
> + Fix comment style
> + Fix typo when assigning element paths in attach_req_node
> + Fix setting app_path and owner during Attach()
> + Fix typo CompanyID property validation
> + Added comments about temporary node usage during Attach()
> + Keep element's Location property optional according to API
>   documentation
> 
> ---
> 
> This patchset streamlines app validation by creating a temporary node
> during Attach, Join and CreateNetwork calls, then validating its
> composition data to:
>  - fit in Config Model Composition Data Get message
>  - declare mandatory models on primary element
>  - declare consecutive element indexes
> 
> During Attach call, temporary composition data is also compared with
> data generated for existing node, guaranteeing immutablity required
> by
> the specification.
> 
> Michał Lowas-Rzechonek (5):
>   mesh: Convert void pointers to anonymous unions in
> managed_obj_request
>   mesh: Validate application by comparing composition data
>   mesh: Keep element and model lists sorted and unique
>   mesh: Check that element indexes are consecutive
>   mesh: Check that config server is present in primary element
> 
>  mesh/mesh-defs.h |   2 +
>  mesh/node.c      | 556 ++++++++++++++++++++++++---------------------
> --
>  2 files changed, 290 insertions(+), 268 deletions(-)
> 

The patch set looks good.
Thanks,
Inga

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3265 bytes --]