All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Stotland, Inga" <inga.stotland@intel.com>
Cc: "luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
	"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>
Subject: Re: [PATCH BlueZ 0/5 v2] mesh: Save/restore network keys
Date: Tue, 12 Feb 2019 23:42:21 +0000	[thread overview]
Message-ID: <1550014939.29883.0.camel@intel.com> (raw)
In-Reply-To: <20190207035537.20375-1-inga.stotland@intel.com>

Patch set applied


On Wed, 2019-02-06 at 19:55 -0800, Inga Stotland wrote:
> Rev.2: addressed Brina's comments.
> 
> This set of patches fixes the network key add/update processing.
> Network keys need to be saved to a local node configuration file
> when:
> 	- a new node is provisioned
> 	- new network key are added by a configuration client
>     - existing network key is updated by a configuration client
> 	  during key refresh procedure.
> 
> Also, each saved network key is accompanied by a proper key
> refresh phase setting.
> 
> Inga Stotland (5):
>   mesh: Separate functions for net key add and update
>   mesh: Add function to restore net key state from storage
>   mesh: Declare internal functions as static
>   mesh: Save key refresh phase state to node config file
>   mesh: Save newly added or updated net key to config file
> 
>  mesh/cfgmod-server.c |   8 +-
>  mesh/mesh-db.c       | 178 +++++++++++++++++-----------
>  mesh/mesh-db.h       |   6 +-
>  mesh/net.c           | 268 +++++++++++++++++++++++++++----------------
>  mesh/net.h           |  12 +-
>  mesh/node.c          |  19 ++-
>  mesh/storage.c       |  22 ++--
>  mesh/storage.h       |   7 +-
>  8 files changed, 326 insertions(+), 194 deletions(-)
> 

      parent reply	other threads:[~2019-02-12 23:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07  3:55 [PATCH BlueZ 0/5 v2] mesh: Save/restore network keys Inga Stotland
2019-02-07  3:55 ` [PATCH BlueZ 1/5 v2] mesh: Separate functions for net key add and update Inga Stotland
2019-02-07  3:55 ` [PATCH BlueZ 2/5 v2] mesh: Add function to restore net key state from storage Inga Stotland
2019-02-07  3:55 ` [PATCH BlueZ 3/5 v2] mesh: Declare internal functions as static Inga Stotland
2019-02-07  3:55 ` [PATCH BlueZ 4/5 v2] mesh: Save key refresh phase state to node config file Inga Stotland
2019-02-07  3:55 ` [PATCH BlueZ 5/5 v2] mesh: Save newly added or updated net key to " Inga Stotland
2019-02-12 23:42 ` Gix, Brian [this message]

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=1550014939.29883.0.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@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.