From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ 0/3] mesh: Save/restore application keys
Date: Wed, 13 Feb 2019 19:45:24 -0800 [thread overview]
Message-ID: <20190214034527.6310-1-inga.stotland@intel.com> (raw)
This set of patches fixes the application key add/update processing.
An application key needs to be saved to a local node configuration file
when:
- a new application key is added by a configuration client
- an existing application key is updated by a configuration client
during key refresh procedure.
Also, fix error codes for AppKey List operation
Inga Stotland (3):
mesh: Separate functions for app key add and update
mesh: Save newly added or updated app key to config file
mesh: Return correct error code for Appkey List command
mesh/appkey.c | 92 ++++++++++++++++++++++---------------
mesh/appkey.h | 4 +-
mesh/cfgmod-server.c | 8 +++-
mesh/mesh-db.c | 107 ++++++++++++++++++++-----------------------
mesh/mesh-db.h | 4 +-
mesh/storage.c | 5 +-
6 files changed, 120 insertions(+), 100 deletions(-)
--
2.17.2
next reply other threads:[~2019-02-14 3:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 3:45 Inga Stotland [this message]
2019-02-14 3:45 ` [PATCH BlueZ 1/3] mesh: Separate functions for app key add and update Inga Stotland
2019-02-14 3:45 ` [PATCH BlueZ 2/3] mesh: Save newly added or updated app key to config file Inga Stotland
2019-02-14 3:45 ` [PATCH BlueZ 3/3] mesh: Return correct error code for AppKey List command Inga Stotland
2019-02-19 21:30 ` [PATCH BlueZ 0/3] mesh: Save/restore application keys 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=20190214034527.6310-1-inga.stotland@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.