From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Cc: "luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>
Subject: Re: [PATCH BlueZ 0/2] Start implementing mesh Management interface
Date: Wed, 15 May 2019 16:45:42 +0000 [thread overview]
Message-ID: <1557938741.32584.3.camel@intel.com> (raw)
In-Reply-To: <20190514225407.29594-1-inga.stotland@intel.com>
Patch-set applied
On Tue, 2019-05-14 at 15:54 -0700, Inga Stotland wrote:
> This patch set ads a sketleton for org.bluez.mesh.Management1 interface.
> Also, adds check for the existence of the provisioning agent for an
> attaching node: this information will be further used to validate
> number of method calls on Management interface
>
> Inga Stotland (2):
> mesh: Add check for org.bluez.mesh.Provisioner1 interface
> mesh: Add skeleton for org.bluez.mesh.Management1 interface
>
> Makefile.mesh | 1 +
> mesh/dbus.c | 12 ++-
> mesh/error.h | 1 +
> mesh/manager.c | 266 +++++++++++++++++++++++++++++++++++++++++++++++++
> mesh/manager.h | 20 ++++
> mesh/mesh.h | 4 +-
> mesh/node.c | 5 +-
> 7 files changed, 303 insertions(+), 6 deletions(-)
> create mode 100644 mesh/manager.c
> create mode 100644 mesh/manager.h
>
prev parent reply other threads:[~2019-05-15 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 22:54 [PATCH BlueZ 0/2] Start implementing mesh Management interface Inga Stotland
2019-05-14 22:54 ` [PATCH BlueZ 1/2] mesh: Add check for org.bluez.mesh.Provisioner1 interface Inga Stotland
2019-05-14 22:54 ` [PATCH BlueZ 2/2] mesh: Add skeleton for org.bluez.mesh.Management1 interface Inga Stotland
2019-05-15 16:45 ` 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=1557938741.32584.3.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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).