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: brian.gix@intel.com, inga.stotland@intel.com
Subject: [PATCH BlueZ 0/2] mesh: Streamline Key Refresh finalization
Date: Wed, 28 Aug 2019 15:48:49 -0700	[thread overview]
Message-ID: <20190828224851.2201-1-brian.gix@intel.com> (raw)

All App key refresh finalization will happen when the bound Net Key is
finalized.

Brian Gix (2):
  doc: Remove uneeded dbus API for App Key Refresh
  mesh: Automate AppKey update on KR phase 2-->3-->0

 doc/mesh-api.txt | 19 ---------------
 mesh/keyring.c   | 63 ++++++++++++++++++++++++++++++++++++++++++++++++
 mesh/keyring.h   |  1 +
 mesh/manager.c   | 39 ++++++------------------------
 4 files changed, 72 insertions(+), 50 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-08-28 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 22:48 Brian Gix [this message]
2019-08-28 22:48 ` [PATCH BlueZ 1/2] doc: Remove uneeded dbus API for App Key Refresh Brian Gix
2019-08-28 22:48 ` [PATCH BlueZ 2/2] mesh: Automate AppKey update on KR phase 2-->3-->0 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=20190828224851.2201-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).