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, brian.gix@intel.com
Subject: [PATCH BlueZ v2 0/5] mesh: Add App and Net Key Refresh keyring back-end
Date: Wed, 22 May 2019 12:54:23 -0700	[thread overview]
Message-ID: <20190522195428.1901-1-brian.gix@intel.com> (raw)

Version 2 is a patchset with some pre-staging cleanup and breaking the
patches into functional sets.

Patches are order dependant (apply in composed order)

Brian Gix (5):
  mesh: Add new required method for Key Refresh proc
  mesh: Centralize definition of PRIMARY_NET_IDX
  mesh: Implement Net Key keyring storage handling
  mesh: Implement App Key keyring storage handling
  mesh: Implement Key Refresh Phasing in keyring

 doc/mesh-api.txt |  26 ++++++-
 mesh/manager.c   | 226 +++++++++++++++++++++++++++++++++++++++++++++++--------
 mesh/mesh-defs.h |   1 +
 mesh/node.c      |  12 ++-
 4 files changed, 227 insertions(+), 38 deletions(-)

-- 
2.14.5


             reply	other threads:[~2019-05-22 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 19:54 Brian Gix [this message]
2019-05-22 19:54 ` [PATCH BlueZ v2 1/5] mesh: Add new required method for Key Refresh proc Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 2/5] mesh: Centralize definition of PRIMARY_NET_IDX Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 3/5] mesh: Implement Net Key keyring storage handling Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 4/5] mesh: Implement App " Brian Gix
2019-05-22 19:54 ` [PATCH BlueZ v2 5/5] mesh: Implement Key Refresh Phasing in keyring 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=20190522195428.1901-1-brian.gix@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 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).