linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.von.dentz@intel.com, marcel@holtmann.org,
	brian.gix@intel.com, Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ v2 1/2] mesh: Rename mesh daemon executable to bluetooth-meshd
Date: Fri, 18 Jan 2019 19:58:36 -0800	[thread overview]
Message-ID: <20190119035837.6053-2-inga.stotland@intel.com> (raw)
In-Reply-To: <20190119035837.6053-1-inga.stotland@intel.com>

---
 Makefile.mesh | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Makefile.mesh b/Makefile.mesh
index ea6c5e939..66854e0bf 100644
--- a/Makefile.mesh
+++ b/Makefile.mesh
@@ -22,9 +22,9 @@ mesh_sources = mesh/mesh.h mesh/mesh.c \
 				mesh/prov-acceptor.c mesh/prov-initiator.c \
 				mesh/pb-adv.h mesh/pb-adv.c \
 				mesh/mesh-defs.h
-libexec_PROGRAMS += mesh/meshd
+libexec_PROGRAMS += mesh/bluetooth-meshd
 
-mesh_meshd_SOURCES = $(mesh_sources) mesh/main.c
-mesh_meshd_LDADD = src/libshared-ell.la $(ell_ldadd) -ljson-c
-mesh_meshd_DEPENDENCIES = $(ell_dependencies) src/libshared-ell.la
+mesh_bluetooth_meshd_SOURCES = $(mesh_sources) mesh/main.c
+mesh_bluetooth_meshd_LDADD = src/libshared-ell.la $(ell_ldadd) -ljson-c
+mesh_bluetooth_meshd_DEPENDENCIES = $(ell_dependencies) src/libshared-ell.la
 endif
-- 
2.17.2


  reply	other threads:[~2019-01-19  3:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  3:58 [PATCH BlueZ v2 0/2] Updated mesh D-Bus policy patch Inga Stotland
2019-01-19  3:58 ` Inga Stotland [this message]
2019-01-19  3:58 ` [PATCH BlueZ v2 2/2] mesh: Add D-Bus policy for Bluetooth mesh daemon Inga Stotland
2019-02-04 20:12 ` [PATCH BlueZ v2 0/2] Updated mesh D-Bus policy patch Gix, Brian

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=20190119035837.6053-2-inga.stotland@intel.com \
    --to=inga.stotland@intel.com \
    --cc=brian.gix@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.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;
as well as URLs for NNTP newsgroup(s).