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>
Subject: Re: [PATCH BlueZ 00/20] Mesh Configuration Database
Date: Mon, 27 Sep 2021 20:27:22 +0000	[thread overview]
Message-ID: <ff95e7b41e93c79f176ca9f841ec781e980bd58f.camel@intel.com> (raw)
In-Reply-To: <20210923032603.50536-1-inga.stotland@intel.com>

With very minor tweeks (to avoid introducing, then removing obsolete naming) Patchset has been applied.

On Wed, 2021-09-22 at 20:25 -0700, Inga Stotland wrote:
> This patch set (I apologize for its size, but this cannot be helped)
> implements support for the newly published Mesh Configuration Database
> Profile.
> 
> The changes are mostly contained to tools/mesh-cfgclient.c and tools/mesh
> subdirectory. The only exception is the introduction of a new D-Bus mesh
> API method ExportKeys() on org.bluez.mesh.Management1 interface.
> 
> The new functionality allows to export a snapshot of mesh state
> from the point of view of mesh provisioner/configuration manager in
> a standard format that can be used for to transferring the "ownership"
> of the mesh configuration to another provisioner/configuration manager.
> 
> The changes break backwards compatibility with for the previous
> versions of config-db.json that were generated when using
> mesh-cfgclient tool. This can be amended by manually correcting the
> field names and property values.
> 
> Inga Stotland (20):
>   tools/mesh-cfgclient: Save provisioner info
>   tools/mesh-cfgclient: Add timestamp to config database
>   tools/mesh-cfgclient: Update stored NetKey and AppKey
>   tools/mesh-cfgclient: Keep track of updated keys
>   tools/mesh: Add new info to stored remote nodes
>   tools/mesh-cfgclient: Overwrite config values when adding new ones
>   tools/mesh-cfgclient: Store remote node's model bindings
>   tools/mesh-cfgclient: Store remote node's model subs
>   tools/mesh-cfgclient: Disallow model commands w/o composition
>   tools/mesh-cfgclient: Store remote's model publication info
>   tools/mesh-cfgclient: Check the result of config save
>   tools/mesh-cfgclient: Rename mesh-db APIs for consistency
>   tools/mesh-cfgclient: Save remote node feature setting
>   tools/mesh-cfgclient: Store remote's heartbeat sub/pub
>   tools/mesh-cfgclient: Add group parent address for DB compliance
>   doc/mesh-api: Add ExportKeys call
>   mesh: Implement ExportKeys() method
>   tools/mesh-cfgclient: Store UUIDs in standard format
>   tools/mesh-cfgclient: Excluded addresses property
>   tools/mesh-cfgclient: Export configuration database
> 
>  doc/mesh-api.txt       |   56 ++
>  mesh/keyring.c         |  286 ++++++++-
>  mesh/keyring.h         |    2 +
>  mesh/manager.c         |   35 ++
>  tools/mesh-cfgclient.c |  212 ++++++-
>  tools/mesh/cfgcli.c    |  284 ++++++---
>  tools/mesh/keys.c      |    4 +-
>  tools/mesh/mesh-db.c   | 1260 +++++++++++++++++++++++++++++++++++++---
>  tools/mesh/mesh-db.h   |   66 ++-
>  tools/mesh/model.h     |   13 +-
>  tools/mesh/remote.c    |  205 +++++--
>  tools/mesh/remote.h    |   11 +-
>  12 files changed, 2206 insertions(+), 228 deletions(-)
> 


      parent reply	other threads:[~2021-09-27 20:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  3:25 [PATCH BlueZ 00/20] Mesh Configuration Database Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 01/20] tools/mesh-cfgclient: Save provisioner info Inga Stotland
2021-09-23  4:00   ` Mesh Configuration Database bluez.test.bot
2021-09-23  4:14     ` Tedd Ho-Jeong An
2021-09-23 16:52   ` bluez.test.bot
2021-09-23  3:25 ` [PATCH BlueZ 02/20] tools/mesh-cfgclient: Add timestamp to config database Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 03/20] tools/mesh-cfgclient: Update stored NetKey and AppKey Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 04/20] tools/mesh-cfgclient: Keep track of updated keys Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 05/20] tools/mesh: Add new info to stored remote nodes Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 06/20] tools/mesh-cfgclient: Overwrite config values when adding new ones Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 07/20] tools/mesh-cfgclient: Store remote node's model bindings Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 08/20] tools/mesh-cfgclient: Store remote node's model subs Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 09/20] tools/mesh-cfgclient: Disallow model commands w/o composition Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 10/20] tools/mesh-cfgclient: Store remote's model publication info Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 11/20] tools/mesh-cfgclient: Check the result of config save Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 12/20] tools/mesh-cfgclient: Rename mesh-db APIs for consistency Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 13/20] tools/mesh-cfgclient: Save remote node feature setting Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 14/20] tools/mesh-cfgclient: Store remote's heartbeat sub/pub Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 15/20] tools/mesh-cfgclient: Add group parent address for DB compliance Inga Stotland
2021-09-23  3:25 ` [PATCH BlueZ 16/20] doc/mesh-api: Add ExportKeys call Inga Stotland
2021-09-23  3:26 ` [PATCH BlueZ 17/20] mesh: Implement ExportKeys() method Inga Stotland
2021-09-23  3:26 ` [PATCH BlueZ 18/20] tools/mesh-cfgclient: Store UUIDs in standard format Inga Stotland
2021-09-23  3:26 ` [PATCH BlueZ 19/20] tools/mesh-cfgclient: Excluded addresses property Inga Stotland
2021-09-23  3:26 ` [PATCH BlueZ 20/20] tools/mesh-cfgclient: Export configuration database Inga Stotland
2021-09-27 20:27 ` 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=ff95e7b41e93c79f176ca9f841ec781e980bd58f.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@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 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.