From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ 0/4] Allow some composition fields update
Date: Fri, 8 May 2020 17:00:20 -0700 [thread overview]
Message-ID: <20200509000024.5704-1-inga.stotland@intel.com> (raw)
This patchset modifies how we verify the integrity of an existing
node when processing Attach() call.
The changes:
- Vericifaction includes only element/models relationship: this should
stay constant during node's lifetime.
- Allow updating of CID, PID, VID and CRPL.
- Some general cleanup related to saving node configuration.
Inga Stotland (4):
mesh: On node attach, verify element/model composition only
mesh: Avoid saving duplicate fields in node config
mesh: Allow updating CID, PID, VID & CRPL on node attach
mesh: Remove redundant call to save node configuration
mesh/mesh-config-json.c | 56 +++++++++++++++++++++++++++++++++--------
mesh/mesh-config.h | 4 +++
mesh/node.c | 29 +++++++++++++++------
3 files changed, 71 insertions(+), 18 deletions(-)
--
2.21.3
next reply other threads:[~2020-05-09 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 0:00 Inga Stotland [this message]
2020-05-09 0:00 ` [PATCH BlueZ 1/4] mesh: On node attach, verify element/model composition only Inga Stotland
2020-05-09 13:49 ` Gix, Brian
2020-05-14 17:05 ` Gix, Brian
2020-05-09 0:00 ` [PATCH BlueZ 2/4] mesh: Avoid saving duplicate fields in node config Inga Stotland
2020-05-09 0:00 ` [PATCH BlueZ 3/4] mesh: Allow updating CID, PID, VID & CRPL on node attach Inga Stotland
2020-05-09 0:00 ` [PATCH BlueZ 4/4] mesh: Remove redundant call to save node configuration Inga Stotland
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=20200509000024.5704-1-inga.stotland@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@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).