From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "ludwig.nussel@suse.de" <ludwig.nussel@suse.de>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ v4 0/3] mesh - Service and Installation
Date: Thu, 6 Jun 2019 19:03:38 +0000 [thread overview]
Message-ID: <1559847816.7839.0.camel@intel.com> (raw)
In-Reply-To: <20190604202852.12656-1-brian.gix@intel.com>
These three patches applied, Thanks
On Tue, 2019-06-04 at 13:28 -0700, Brian Gix wrote:
> This patch set of changes from Inga and Ludwig are needed to install
> the bluetooth-mesh daemon as a systemd service, with access to D-bus.
>
> Ludwig's patch from April fixes a problem with installation locations
> for *all* of BlueZ, and Inga's adds the bluetooth-mesh service.
>
>
> Inga Stotland (2):
> build: Add support for systemd bluetooth-mesh service
> mesh: Do not daemonize, run in foreground or as service
>
> Ludwig Nussel (1):
> install: Fix installations to pkglibexecdir
>
> Makefile.am | 4 ++--
> Makefile.mesh | 16 +++++++++++++---
> Makefile.obexd | 2 +-
> Makefile.tools | 2 +-
> mesh/bluetooth-mesh.service.in | 17 +++++++++++++++++
> mesh/main.c | 17 ++++++-----------
> mesh/org.bluez.mesh.service | 5 +++++
> 7 files changed, 45 insertions(+), 18 deletions(-)
> create mode 100644 mesh/bluetooth-mesh.service.in
> create mode 100644 mesh/org.bluez.mesh.service
>
prev parent reply other threads:[~2019-06-06 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 20:28 [PATCH BlueZ v4 0/3] mesh - Service and Installation Brian Gix
2019-06-04 20:28 ` [PATCH BlueZ v4 1/3] install: Fix installations to pkglibexecdir Brian Gix
2019-06-04 20:28 ` [PATCH BlueZ v4 2/3] build: Add support for systemd bluetooth-mesh service Brian Gix
2019-06-04 20:28 ` [PATCH BlueZ v4 3/3] mesh: Do not daemonize, run in foreground or as service Brian Gix
2019-06-06 19:03 ` Gix, Brian [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=1559847816.7839.0.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.