linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, marcel@holtmann.org,
	brian.gix@intel.com, johan.hedberg@gmail.com,
	michal.lowas-rzechonek@silvair.com
Subject: [PATCH BlueZ v6 0/1] mesh: Add APIs for Provisioner and Config Client
Date: Thu, 18 Apr 2019 15:15:17 -0700	[thread overview]
Message-ID: <20190418221518.13652-1-brian.gix@intel.com> (raw)

Version 6 is a further refinement based on reflector feedback, and
adds methods to import externally derived App and Net keys as well
to a local nodes Config Client key storage.

Brian Gix (1):
  mesh: Add APIs for Provisioner and Config Client

 doc/mesh-api.txt | 492 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 478 insertions(+), 14 deletions(-)

-- 
2.14.5


             reply	other threads:[~2019-04-18 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 22:15 Brian Gix [this message]
2019-04-18 22:15 ` [PATCH BlueZ v6 1/1] mesh: Add APIs for Provisioner and Config Client Brian Gix

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=20190418221518.13652-1-brian.gix@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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 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).