From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v6 0/5] Use composition data to validate app against the
Date: Fri, 26 Jul 2019 08:36:01 +0200 [thread overview]
Message-ID: <20190726063606.19359-1-michal.lowas-rzechonek@silvair.com> (raw)
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(-)
--
2.19.1
next reply other threads:[~2019-07-26 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:36 Michał Lowas-Rzechonek [this message]
2019-07-26 6:36 ` [PATCH BlueZ v6 1/5] mesh: Convert void pointers to anonymous unions in managed_obj_request Michał Lowas-Rzechonek
2019-07-26 6:36 ` [PATCH BlueZ v6 2/5] mesh: Validate application by comparing composition data Michał Lowas-Rzechonek
2019-07-26 6:36 ` [PATCH BlueZ v6 3/5] mesh: Keep element and model lists sorted and unique Michał Lowas-Rzechonek
2019-07-26 6:36 ` [PATCH BlueZ v6 4/5] mesh: Check that element indexes are consecutive Michał Lowas-Rzechonek
2019-07-26 6:36 ` [PATCH BlueZ v6 5/5] mesh: Check that config server is present in primary element Michał Lowas-Rzechonek
2019-07-26 14:24 ` [PATCH BlueZ v6 0/5] Use composition data to validate app against the Stotland, Inga
2019-07-26 16:19 ` Gix, Brian
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=20190726063606.19359-1-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).