public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@intel.com>
To: "Stotland, Inga" <inga.stotland@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
	"marcel@holtmann.org" <marcel@holtmann.org>,
	"Gix, Brian" <brian.gix@intel.com>
Subject: Re: [PATCH BlueZ 0/2] Directory re-org for meshctl tool
Date: Mon, 2 Jul 2018 19:08:34 +0300	[thread overview]
Message-ID: <20180702160834.GA17202@x1c.home> (raw)
In-Reply-To: <1530165033.4244.11.camel@intel.com>

Hi Inga,

The patches look fine to me, but we should get an ack from Marcel before
applying.

Johan

On Thu, Jun 28, 2018, Stotland, Inga wrote:
> Ping
> 
> On Thu, 2018-06-21 at 23:31 -0700, Inga Stotland wrote:
> > This set of patches moves mechctl tool code from under bluez/mesh
> > into tools directory.
> > 
> > mesh directory will be re-established with the implementation of mesh
> > daemon.
> > 
> > Inga Stotland (2):
> >   tools: Move meshctl tool under tools directory
> >   tools: Move meshctl sources under tools/mesh directory
> > 
> >  Makefile.tools                       | 48 ++++++++++++++++++------------------
> >  {mesh => tools/mesh}/README          |  0
> >  {mesh => tools/mesh}/agent.c         |  4 +--
> >  {mesh => tools/mesh}/agent.h         |  0
> >  {mesh => tools/mesh}/config-client.c | 14 +++++------
> >  {mesh => tools/mesh}/config-model.h  |  0
> >  {mesh => tools/mesh}/config-server.c | 14 +++++------
> >  {mesh => tools/mesh}/crypto.c        |  4 +--
> >  {mesh => tools/mesh}/crypto.h        |  0
> >  {mesh => tools/mesh}/gatt.c          | 10 ++++----
> >  {mesh => tools/mesh}/gatt.h          |  0
> >  {mesh => tools/mesh}/keys.h          |  0
> >  {mesh => tools/mesh}/local_node.json |  0
> >  {mesh => tools/mesh}/mesh-net.h      |  0
> >  {mesh => tools/mesh}/net.c           | 16 ++++++------
> >  {mesh => tools/mesh}/net.h           |  0
> >  {mesh => tools/mesh}/node.c          | 16 ++++++------
> >  {mesh => tools/mesh}/node.h          |  0
> >  {mesh => tools/mesh}/onoff-model.c   | 14 +++++------
> >  {mesh => tools/mesh}/onoff-model.h   |  0
> >  {mesh => tools/mesh}/prov-db.c       | 14 +++++------
> >  {mesh => tools/mesh}/prov-db.h       |  0
> >  {mesh => tools/mesh}/prov.c          | 16 ++++++------
> >  {mesh => tools/mesh}/prov.h          |  0
> >  {mesh => tools/mesh}/prov_db.json    |  0
> >  {mesh => tools/mesh}/util.c          |  6 ++---
> >  {mesh => tools/mesh}/util.h          |  0
> >  mesh/main.c => tools/meshctl.c       |  0
> >  28 files changed, 88 insertions(+), 88 deletions(-)
> >  rename {mesh => tools/mesh}/README (100%)
> >  rename {mesh => tools/mesh}/agent.c (98%)
> >  rename {mesh => tools/mesh}/agent.h (100%)
> >  rename {mesh => tools/mesh}/config-client.c (99%)
> >  rename {mesh => tools/mesh}/config-model.h (100%)
> >  rename {mesh => tools/mesh}/config-server.c (94%)
> >  rename {mesh => tools/mesh}/crypto.c (99%)
> >  rename {mesh => tools/mesh}/crypto.h (100%)
> >  rename {mesh => tools/mesh}/gatt.c (98%)
> >  rename {mesh => tools/mesh}/gatt.h (100%)
> >  rename {mesh => tools/mesh}/keys.h (100%)
> >  rename {mesh => tools/mesh}/local_node.json (100%)
> >  rename {mesh => tools/mesh}/mesh-net.h (100%)
> >  rename {mesh => tools/mesh}/net.c (99%)
> >  rename {mesh => tools/mesh}/net.h (100%)
> >  rename {mesh => tools/mesh}/node.c (98%)
> >  rename {mesh => tools/mesh}/node.h (100%)
> >  rename {mesh => tools/mesh}/onoff-model.c (96%)
> >  rename {mesh => tools/mesh}/onoff-model.h (100%)
> >  rename {mesh => tools/mesh}/prov-db.c (99%)
> >  rename {mesh => tools/mesh}/prov-db.h (100%)
> >  rename {mesh => tools/mesh}/prov.c (98%)
> >  rename {mesh => tools/mesh}/prov.h (100%)
> >  rename {mesh => tools/mesh}/prov_db.json (100%)
> >  rename {mesh => tools/mesh}/util.c (98%)
> >  rename {mesh => tools/mesh}/util.h (100%)
> >  rename mesh/main.c => tools/meshctl.c (100%)
> > 

  reply	other threads:[~2018-07-02 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  6:31 [PATCH BlueZ 0/2] Directory re-org for meshctl tool Inga Stotland
2018-06-22  6:31 ` [PATCH BlueZ 1/2] tools: Move meshctl tool under tools directory Inga Stotland
2018-06-22  6:32 ` [PATCH BlueZ 2/2] tools: Move meshctl sources under tools/mesh directory Inga Stotland
2018-06-28  5:50 ` [PATCH BlueZ 0/2] Directory re-org for meshctl tool Stotland, Inga
2018-07-02 16:08   ` Johan Hedberg [this message]
2018-07-06 10:30 ` Marcel Holtmann
2018-07-06 10:41   ` Johan Hedberg
2018-07-06 10:46     ` Marcel Holtmann
2018-07-06 11:05 ` Marcel Holtmann

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=20180702160834.GA17202@x1c.home \
    --to=johan.hedberg@intel.com \
    --cc=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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