From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ 0/4] Mesh send/publish API change
Date: Sun, 23 Aug 2020 20:54:11 -0700 [thread overview]
Message-ID: <20200824035415.13420-1-inga.stotland@intel.com> (raw)
This patch set modifies Send, DevKeySend, Publish & VendorPublish
methods on bleuz.mesh.Node interface to include additional argument
"options".
This new argument is a dictionary that currently has only one
new key word defined:
"ForceSegmented" - to force small payloads to be sent as
one-segment messages
Other key words may be defined in future to accommodate evolving
requirements of Mesh Profile specification.
Inga Stotland (4):
doc/mesh-api: Add "options" dictionary to Send/Publish
mesh: Handle "options" dictionary in Send/Publish methods
tools/mesh-cfglient: Add "options" to Send/DevKeySend
test/test-mesh: Add "options" to Send/Publish
doc/mesh-api.txt | 47 ++++++++++++++++++--
mesh/cfgmod-server.c | 2 +-
mesh/model.c | 6 +--
mesh/model.h | 9 ++--
mesh/node.c | 99 +++++++++++++++++++++++++++++-------------
test/test-mesh | 10 ++++-
tools/mesh-cfgclient.c | 8 ++++
7 files changed, 136 insertions(+), 45 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-24 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 3:54 Inga Stotland [this message]
2020-08-24 3:54 ` [PATCH BlueZ 1/4] doc/mesh-api: Add "options" dictionary to Send/Publish Inga Stotland
2020-08-24 4:27 ` [BlueZ,1/4] " bluez.test.bot
2020-08-24 15:04 ` [PATCH BlueZ 1/4] " Gix, Brian
2020-08-24 3:54 ` [PATCH BlueZ 2/4] mesh: Handle "options" dictionary in Send/Publish methods Inga Stotland
2020-08-24 3:54 ` [PATCH BlueZ 3/4] tools/mesh-cfglient: Add "options" to Send/DevKeySend Inga Stotland
2020-08-24 3:54 ` [PATCH BlueZ 4/4] test/test-mesh: Add "options" to Send/Publish Inga Stotland
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=20200824035415.13420-1-inga.stotland@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@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).