From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ 0/2] Minor fixes and clean up
Date: Thu, 6 Jun 2019 19:32:22 +0000 [thread overview]
Message-ID: <8cf1f8c82d27176ab5459b33d65c31a2750033e9.camel@intel.com> (raw)
In-Reply-To: <20190606011832.18801-1-inga.stotland@intel.com>
Patches Applied
On Wed, 2019-06-05 at 18:18 -0700, Inga Stotland wrote:
> Cleanup coding style. Don't check the return values of l_new() and
> l_queue_new().
> Add check for the presense of "elements" property in node
> configuration
> (it's mandatory)
>
> Inga Stotland (2):
> mesh: Make "elements" mandatory in node configuration
> mesh: Clean up style
>
> mesh/mesh-db.c | 23 +++++++++--------------
> mesh/model.c | 25 +++++++++++++------------
> 2 files changed, 22 insertions(+), 26 deletions(-)
>
prev parent reply other threads:[~2019-06-06 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 1:18 [PATCH BlueZ 0/2] Minor fixes and clean up Inga Stotland
2019-06-06 1:18 ` [PATCH BlueZ 1/2] mesh: Make "elements" mandatory in node configuration Inga Stotland
2019-06-06 1:18 ` [PATCH BlueZ 2/2] mesh: Clean up style Inga Stotland
2019-06-06 19:32 ` 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=8cf1f8c82d27176ab5459b33d65c31a2750033e9.camel@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).