From: Johan Hedberg <johan.hedberg@intel.com>
To: Inga Stotland <inga.stotland@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] mesh:meshctl: make model parsing more manageable
Date: Tue, 19 Dec 2017 17:52:16 +0100 [thread overview]
Message-ID: <20171219165216.GA31289@x1c> (raw)
In-Reply-To: <20171218203551.6142-1-inga.stotland@intel.com>
Hi Inga,
On Mon, Dec 18, 2017, Inga Stotland wrote:
> Extract functionality for finding an existing model from
> parse_configuration_models() into new function find_configured_model().
> This removes confusing logic from overloaded implementation of
> parse_configuration_models().
> ---
> mesh/prov-db.c | 54 ++++++++++++++++++++++++++++++++++++++++++------------
> 1 file changed, 42 insertions(+), 12 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2017-12-19 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 20:35 [PATCH BlueZ] mesh:meshctl: make model parsing more manageable Inga Stotland
2017-12-19 8:41 ` Steve Brown
2017-12-19 11:46 ` Luiz Augusto von Dentz
2017-12-19 16:52 ` Johan Hedberg [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=20171219165216.GA31289@x1c \
--to=johan.hedberg@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).