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/4] Cleanup of org.bluez.mesh.Network1 interface
Date: Thu, 2 May 2019 16:01:26 +0000 [thread overview]
Message-ID: <1556812884.28287.0.camel@intel.com> (raw)
In-Reply-To: <20190429194509.3378-1-inga.stotland@intel.com>
Patch-set applied
On Mon, 2019-04-29 at 12:45 -0700, Inga Stotland wrote:
> This set of patches tightens the existing implementation of Join() and
> Attach() methods. Some redundacies are removed, common code is combined and
> validation of node composition is added for Attach method.
>
> Inga Stotland (4):
> mesh: Remove Node interface if node owner disconnects
> mesh: Clean up processing of Attach() method
> mesh: Consolidate processing of mesh element properties
> mesh: Unify processing of GetManagedObjects result
>
> mesh/mesh-defs.h | 2 +
> mesh/mesh.c | 69 +++---
> mesh/node.c | 558 ++++++++++++++++++++++++++---------------------
> mesh/node.h | 9 +-
> 4 files changed, 344 insertions(+), 294 deletions(-)
>
prev parent reply other threads:[~2019-05-02 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:45 [PATCH BlueZ 0/4] Cleanup of org.bluez.mesh.Network1 interface Inga Stotland
2019-04-29 19:45 ` [PATCH BlueZ 1/4] mesh: Remove Node interface if node owner disconnects Inga Stotland
2019-04-29 19:45 ` [PATCH BlueZ 2/4] mesh: Clean up processing of Attach() method Inga Stotland
2019-04-29 19:45 ` [PATCH BlueZ 3/4] mesh: Consolidate processing of mesh element properties Inga Stotland
2019-04-29 19:45 ` [PATCH BlueZ 4/4] mesh: Unify processing of GetManagedObjects result Inga Stotland
2019-05-02 16:01 ` 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=1556812884.28287.0.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).