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 v2 1/2] doc: Remove uneeded dbus API for App Key Refresh
Date: Thu, 5 Sep 2019 14:11:48 -0700 [thread overview]
Message-ID: <20190905211149.26255-2-brian.gix@intel.com> (raw)
In-Reply-To: <20190905211149.26255-1-brian.gix@intel.com>
---
doc/mesh-api.txt | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 470751f7a..9b9f4e3de 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -627,25 +627,6 @@ Methods:
org.bluez.mesh.Error.DoesNotExist
org.bluez.mesh.Error.Busy
- void CompleteAppKeyUpdate(uint16 app_index)
-
- This method is used by the application at the completion of
- a Key Refresh Procedure. This method should be called for each
- app key being updated during the procedure, and must be
- performed prior to changing the phase of the bound net key
- to phase 3. (See SetKeyPhase() method).
-
- The app_index parameter is a 12-bit value (0x000-0xFFF)
- specifying which app key was updated. Note that the subnet that
- the key is bound to must exist and be in Phase 2.
-
- This call affects the local bluetooth-meshd key database only.
-
- PossibleErrors:
- org.bluez.mesh.Error.Failed
- org.bluez.mesh.Error.InvalidArguments
- org.bluez.mesh.Error.DoesNotExist
-
void DeleteAppKey(uint16 app_index)
This method is used by the application to delete an application
--
2.21.0
next prev parent reply other threads:[~2019-09-05 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 21:11 [PATCH BlueZ v2 0/2] mesh: Streamline Key Refresh finalization Brian Gix
2019-09-05 21:11 ` Brian Gix [this message]
2019-09-05 21:11 ` [PATCH BlueZ v2 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=20190905211149.26255-2-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).