From: Jakub Witowski <jakub.witowski@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/3] Allow to reattach with new composition data
Date: Mon, 20 Jan 2020 17:11:11 +0100 [thread overview]
Message-ID: <20200120161114.6757-1-jakub.witowski@silvair.com> (raw)
This patch allows the application to modify the CID, PID, VID and CRPL in the composition data.
According the Mesh Profile (2.3.4 Elements) the modification of fields other than "Elements" is not prohibited.
Also in my opinion (as you can see in the 1st patch), there is no need to use pointer to the node_composition struct.
The static is more clear and less problematic.
Jakub Witowski (3):
mesh: use static node_comp instead of the pointer
mesh: add composition data setter
mesh: allow to reattach with new composition data
mesh/mesh-config-json.c | 46 +++++++++++++++-----
mesh/mesh-config.h | 2 +
mesh/node.c | 96 +++++++++++++++++++++++++----------------
3 files changed, 96 insertions(+), 48 deletions(-)
--
2.20.1
next reply other threads:[~2020-01-20 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 16:11 Jakub Witowski [this message]
2020-01-20 16:11 ` [PATCH 1/3] mesh: use static node_comp instead of the pointer Jakub Witowski
2020-01-20 16:11 ` [PATCH 2/3] mesh: add composition data setter Jakub Witowski
2020-01-20 16:11 ` [PATCH 3/3] mesh: allow to reattach with new composition data Jakub Witowski
2020-01-20 17:17 ` [PATCH 0/3] Allow " Gix, Brian
2020-01-21 10:59 ` jakub.witowski
2020-01-21 18:21 ` Stotland, Inga
2020-01-21 20:05 ` Michał Lowas-Rzechonek
2020-01-22 13:53 ` jakub.witowski
2020-01-22 18:02 ` Michał Lowas-Rzechonek
2020-01-22 18:03 ` Michał Lowas-Rzechonek
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=20200120161114.6757-1-jakub.witowski@silvair.com \
--to=jakub.witowski@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