From: Johan Hedberg <johan.hedberg@gmail.com>
To: Steve Brown <sbrown@cortland.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] mesh: meshctl: Add subscriptions to node structure and json database
Date: Fri, 16 Feb 2018 12:38:55 +0200 [thread overview]
Message-ID: <20180216103855.GA30338@x1c.lan> (raw)
In-Reply-To: <20180214131832.23518-1-sbrown@cortland.com>
Hi Steve,
On Wed, Feb 14, 2018, Steve Brown wrote:
> sub-add 0101 c000 1000
>
> {
> "modelId":"1000",
> "bind":[
> 1
> ],
> "subscribe":[
> "c000"
> ]
> },
> ---
> mesh/config-client.c | 15 +++++++----
> mesh/node.c | 20 ++++++++++++++-
> mesh/node.h | 2 ++
> mesh/prov-db.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++----
> mesh/prov-db.h | 2 ++
> 5 files changed, 99 insertions(+), 11 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2018-02-16 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:18 [PATCH] mesh: meshctl: Add subscriptions to node structure and json database Steve Brown
2018-02-16 10:38 ` 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=20180216103855.GA30338@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sbrown@cortland.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).