From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: Javier Viguera <javier.viguera@digi.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [jethro][PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd
Date: Tue, 22 Mar 2016 10:37:59 +0000 [thread overview]
Message-ID: <1458643079.3186.4.camel@linux.intel.com> (raw)
In-Reply-To: <56EFDCAC.6080806@digi.com>
Hi Robert,
On Mon, 2016-03-21 at 12:36 +0100, Javier Viguera wrote:
> Hi Joshua
>
> On 03/03/16 12:30, Joshua G Lock wrote:
> > Ah, I hadn't seen that patch as I was only looking at patches
> > tagged
> > jethro. We can consider this change for jethro once it lands in
> > master.
> >
> This has been finally merged into master.
>
> Would you now consider cherry-picking it into *jethro* ?
Could you consider cherry-picking this fix for Jethro?
http://git.openembedded.org/openembedded-core/commit/?id=75c5dc8d4a5506
bf5b89292a96c7b9f91e9d71c8
---
bluez5: allow D-Bus to spawn obexd in systems without systemd
This includes a proper D-Bus service file for obexd in systems that do
not support systemd.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
Thanks,
Joshua
prev parent reply other threads:[~2016-03-22 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 18:14 [jethro][PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd Javier Viguera
2016-03-03 11:07 ` Joshua G Lock
2016-03-03 11:22 ` Viguera, Javier
2016-03-03 11:30 ` Joshua G Lock
2016-03-21 11:36 ` Javier Viguera
2016-03-22 10:37 ` Joshua G Lock [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=1458643079.3186.4.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=javier.viguera@digi.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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.