From: "Gix, Brian" <brian.gix@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ v7 0/3] Implement org.bluez.mesh.Network1.Import() D-Bus API
Date: Thu, 1 Aug 2019 20:28:52 +0000 [thread overview]
Message-ID: <1564691331.19611.0.camel@intel.com> (raw)
In-Reply-To: <20190731071647.27217-1-michal.lowas-rzechonek@silvair.com>
Applied, Thanks
On Wed, 2019-07-31 at 09:16 +0200, Michał Lowas-Rzechonek wrote:
> + Keep defaultTTL and seqNumber optional, but check the format and range
> + Style fixes in mesh-config-json
> + Reworked the API to new signature
> + Removed dependencies on mesh-config
>
>
> *** BLURB HERE ***
>
> Jakub Witowski (1):
> mesh: Extract read_* functions in mesh-config-json
>
> Michał Lowas-Rzechonek (2):
> mesh: Add documentation for Import() D-Bus API
> mesh: Implement Import() D-Bus API of org.bluez.mesh.Network1
> interface
>
> doc/mesh-api.txt | 57 ++++++++++++++------
> mesh/mesh-config-json.c | 83 +++++++++++++++++++++++------
> mesh/mesh.c | 115 +++++++++++++++++++++++++++++++++++++++-
> mesh/node.c | 87 +++++++++++++++++++++++++++++-
> mesh/node.h | 5 ++
> 5 files changed, 314 insertions(+), 33 deletions(-)
>
prev parent reply other threads:[~2019-08-01 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 7:16 [PATCH BlueZ v7 0/3] Implement org.bluez.mesh.Network1.Import() D-Bus API Michał Lowas-Rzechonek
2019-07-31 7:16 ` [PATCH BlueZ v7 1/3] mesh: Extract read_* functions in mesh-config-json Michał Lowas-Rzechonek
2019-07-31 7:16 ` [PATCH BlueZ v7 2/3] mesh: Add documentation for Import() D-Bus API Michał Lowas-Rzechonek
2019-07-31 7:16 ` [PATCH BlueZ v7 3/3] mesh: Implement Import() D-Bus API of org.bluez.mesh.Network1 interface Michał Lowas-Rzechonek
2019-08-01 5:48 ` [PATCH BlueZ v7 0/3] Implement org.bluez.mesh.Network1.Import() D-Bus API Stotland, Inga
2019-08-01 20:28 ` 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=1564691331.19611.0.camel@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.com \
/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).