From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v4 0/2] mesh: Streamline Key Refresh finalization
Date: Tue, 10 Sep 2019 16:41:43 +0000 [thread overview]
Message-ID: <ed48a0384e0e0d49a2dcd48442d50c0d5ea5f418.camel@intel.com> (raw)
In-Reply-To: <20190906162434.7434-1-brian.gix@intel.com>
Patchset Applied
On Fri, 2019-09-06 at 09:24 -0700, Brian Gix wrote:
> All App key refresh finalization will happen when the bound Net Key is
> finalized.
>
> Version 4: Allow a redundent call to set phase 3 (after transition to
> phase 0 complete) by returning successfully, but doing nothing.
>
>
> 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 | 58 ++++++++++++++++++++++++++++++++++++++++++++++++
> mesh/keyring.h | 1 +
> mesh/manager.c | 53 +++++++++++++++++--------------------------
> 4 files changed, 79 insertions(+), 52 deletions(-)
>
prev parent reply other threads:[~2019-09-10 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 16:24 [PATCH BlueZ v4 0/2] mesh: Streamline Key Refresh finalization Brian Gix
2019-09-06 16:24 ` [PATCH BlueZ v4 1/2] doc: Remove uneeded dbus API for App Key Refresh Brian Gix
2019-09-06 16:24 ` [PATCH BlueZ v4 2/2] mesh: Automate AppKey update on KR phase 2-->3-->0 Brian Gix
2019-09-10 16:41 ` 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=ed48a0384e0e0d49a2dcd48442d50c0d5ea5f418.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 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).