From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: "Viguera, Javier" <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: Thu, 03 Mar 2016 11:30:33 +0000 [thread overview]
Message-ID: <1457004633.3025.13.camel@linux.intel.com> (raw)
In-Reply-To: <DA8287CC96892A4EB4FCF4FB3FBDA1AB790570@dor-sms-xch01.digi.com>
On Thu, 2016-03-03 at 11:22 +0000, Viguera, Javier wrote:
> Hi Joshua,
>
> >
> > -----Original Message-----
> > From: Joshua G Lock [mailto:joshua.g.lock@linux.intel.com]
> > Sent: Thursday, March 03, 2016 12:08 PM
> > To: Viguera, Javier; openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [jethro][PATCH] bluez5: allow D-Bus to spawn
> > obexd in systems without systemd
> >
> > This looks like a valid patch for the master branch too?
> Absolutely. That's why I sent both patches together, one for master
> and this one for Jethro.
>
> See the one for master:
>
> http://patchwork.openembedded.org/patch/116389/
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.
>
> By the way, for Jethro I sent also a different patch (master
> backport):
>
> http://patchwork.openembedded.org/patch/116661/
>
> This last one is already in master and it would be great to have it
> in Jethro as well.
I just included this patch in a consolidated Jethro pull request.
Regards,
Joshua
next prev parent reply other threads:[~2016-03-03 11:30 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 [this message]
2016-03-21 11:36 ` Javier Viguera
2016-03-22 10:37 ` Joshua G Lock
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=1457004633.3025.13.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=Javier.Viguera@digi.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.