From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v2 0/9] mesh: Provisioner Initiator added
Date: Sun, 14 Jul 2019 15:47:16 +0000 [thread overview]
Message-ID: <1563119234.9043.0.camel@intel.com> (raw)
In-Reply-To: <20190711225952.1599-1-brian.gix@intel.com>
Applied
On Thu, 2019-07-11 at 15:59 -0700, Brian Gix wrote:
> v2 additions:
> * Style guide changes noted by Michal
> * Additional patch to use packed structures for Mesh Spec specifid OTA messages
>
> The added functionality of this patch set allows any node with a keyring
> provision a new node into the network. It does *not* implement a
> user App that can store a Configuration Database, but it does provide
> extensions to the python test script to test the primitives.
>
> Brian Gix (9):
> doc: Cleanup API Provisioner1 interface
> mesh: Fix support for Provisioner Initiator
> mesh: Add special Beacon handler for Provisioning
> mesh: Expose mapping function for D-Bus errors
> mesh: Expose resources needed by Management1 interface
> mesh: Fix implementation of Provisioner Initiator
> mesh: Implement DBus Provisioning methods
> mesh: Convert provisioning pkts to packed structs
> test: This extends the mesh tool to exercise Provisioning methods
>
> doc/mesh-api.txt | 13 ++-
> mesh/crypto.c | 8 +-
> mesh/crypto.h | 8 +-
> mesh/manager.c | 304 +++++++++++++++++++++++++++++++++++++++++++++++--
> mesh/mesh-io-generic.c | 2 +-
> mesh/mesh-io.c | 6 +-
> mesh/mesh-io.h | 7 +-
> mesh/mesh.c | 10 +-
> mesh/mesh.h | 4 +-
> mesh/node.c | 42 +++++--
> mesh/node.h | 3 +
> mesh/pb-adv.c | 177 +++++++++++++++++-----------
> mesh/pb-adv.h | 3 +-
> mesh/prov-acceptor.c | 158 +++++++++++++------------
> mesh/prov-initiator.c | 283 +++++++++++++++++++++++++++++++++------------
> mesh/prov.h | 51 ++++++++-
> mesh/provision.h | 10 +-
> test/test-mesh | 113 ++++++++++++++++++
> 18 files changed, 946 insertions(+), 256 deletions(-)
>
prev parent reply other threads:[~2019-07-14 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 22:59 [PATCH BlueZ v2 0/9] mesh: Provisioner Initiator added Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 1/9] doc: Cleanup API Provisioner1 interface Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 2/9] mesh: Fix support for Provisioner Initiator Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 3/9] mesh: Add special Beacon handler for Provisioning Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 4/9] mesh: Expose mapping function for D-Bus errors Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 5/9] mesh: Expose resources needed by Management1 interface Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 6/9] mesh: Fix implementation of Provisioner Initiator Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 7/9] mesh: Implement DBus Provisioning methods Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 8/9] mesh: Convert provisioning pkts to packed structs Brian Gix
2019-07-11 22:59 ` [PATCH BlueZ v2 9/9] test: This extends the mesh tool to exercise Provisioning methods Brian Gix
2019-07-12 8:39 ` [PATCH BlueZ v2 0/9] mesh: Provisioner Initiator added Michał Lowas-Rzechonek
2019-07-14 15:47 ` 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=1563119234.9043.0.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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.