linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: sbrown@cortland.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH V4 0/9] mesh: Add configuration commands to meshctl
Date: Mon, 18 Dec 2017 13:17:50 +0100	[thread overview]
Message-ID: <20171218121750.GA25598@x1c> (raw)
In-Reply-To: <20171217105249.7592-1-sbrown@cortland.com>

Hi Steve,

On Sun, Dec 17, 2017, sbrown@cortland.com wrote:
> This complements the Zephyr application located in the Zephyr tree at
> zephyr/samples/boards/nrf52/mesh/onoff-app
> 
> V2: Break each command into a separate commit
> V3: Correct CID usage in pub-set and pub-get
> V4: Correct 7/9 missing break in ident status case stmt
>             compile problem going from V2 to V3
> 
> Steve Brown (9):
>   mesh: meshctl: Change command names to <cmd>-<get/set>
>   mesh: meshctl: Add add/get subscribe
>   mesh: meshctl: Add set heartbeat publish
>   mesh: meshctl: Add get app keys
>   mesh: meshctl: Add get publish
>   mesh: meshctl: Add set/get proxy
>   mesh: meshctl: Add get/set identity
>   mesh: meshctl: Add get/set relay
>   mesh: meshctl: Add Company ID parameter to pub-set and pub-get
> 
>  mesh/config-client.c | 454 ++++++++++++++++++++++++++++++++++++++++++++++++---
>  mesh/net.c           |  20 ++-
>  2 files changed, 448 insertions(+), 26 deletions(-)

Both my and Inga's comments seem to be covered now, so I went ahead and
applied the entire set. Thanks.

Johan

      parent reply	other threads:[~2017-12-18 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 10:52 [PATCH V4 0/9] mesh: Add configuration commands to meshctl sbrown
2017-12-17 10:52 ` [PATCH V4 1/9] mesh: meshctl: Change command names to <cmd>-<get/set> sbrown
2017-12-17 10:52 ` [PATCH V4 2/9] mesh: meshctl: Add add/get subscribe sbrown
2017-12-17 10:52 ` [PATCH V4 3/9] mesh: meshctl: Add set heartbeat publish sbrown
2017-12-17 10:52 ` [PATCH V4 4/9] mesh: meshctl: Add get app keys sbrown
2017-12-17 10:52 ` [PATCH V4 5/9] mesh: meshctl: Add get publish sbrown
2017-12-17 10:52 ` [PATCH V4 6/9] mesh: meshctl: Add set/get proxy sbrown
2017-12-17 10:52 ` [PATCH V4 7/9] mesh: meshctl: Add get/set identity sbrown
2017-12-17 10:52 ` [PATCH V4 8/9] mesh: meshctl: Add get/set relay sbrown
2017-12-17 10:52 ` [PATCH V4 9/9] mesh: meshctl: Add Company ID parameter to pub-set and pub-get sbrown
2017-12-18 12:17 ` 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=20171218121750.GA25598@x1c \
    --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).