From: "Maxin B. John" <maxin.john@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] bluez5: upgrade to 5.37
Date: Tue, 5 Jan 2016 17:21:57 +0200 [thread overview]
Message-ID: <20160105152157.GA31893@mbabyjoh-mobl.fi.intel.com> (raw)
In-Reply-To: <20160105150124.GB2574@jama>
Hi Martin,
On Tue, Jan 05, 2016 at 04:01:24PM +0100, Martin Jansa wrote:
> On Tue, Jan 05, 2016 at 04:08:13PM +0200, Maxin B. John wrote:
> > 5.36 -> 5.37
> >
> > Remove the backported patch:
> > core-profile-Fix-possible-crash-when-registering-pro.patch
> Don't you need to remove
> file://core-profile-Fix-possible-crash-when-registering-pro.patch
> from SRC_URI when you're removing the file?
Yes, that change is present in the patch (based on "ross/mut" branch)
> Can you please add PNBLACKLIST which will blacklist bluez5 when bluez4
> is in DISTRO_FEATURES?
Sure, will do that.
> Like I did for bluez4 in:
> http://git.openembedded.org/meta-openembedded/commit/?id=73ba7cd70f75a898bf4c3f8ae38c9904fc3e4724
>
> Making bluez4 and bluez5 really mutually exclusive would help with
> issues like this one:
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-January/105341.html
Thank you very much for the comments. Will include these changes in v2.
> > Signed-off-by: Maxin B. John <maxin.john@intel.com>
> > ---
> > ...e-Fix-possible-crash-when-registering-pro.patch | 54 ----------------------
> > .../bluez5/{bluez5_5.36.bb => bluez5_5.37.bb} | 5 +-
> > 2 files changed, 2 insertions(+), 57 deletions(-)
> > delete mode 100644 meta/recipes-connectivity/bluez5/bluez5/core-profile-Fix-possible-crash-when-registering-pro.patch
> > rename meta/recipes-connectivity/bluez5/{bluez5_5.36.bb => bluez5_5.37.bb} (83%)
<snip>
> > -SRC_URI += "file://core-profile-Fix-possible-crash-when-registering-pro.patch"
> > -SRC_URI[md5sum] = "9a0ee479cacc44fac68f6a65b1cd3eba"
> > -SRC_URI[sha256sum] = "a343ea1aeb53d3bd139087f3b1c1e1fb70db452d9762cc7a3d23e75962e578f2"
> > +SRC_URI[md5sum] = "33177e5743e24b2b3738f72be64e3ffb"
> > +SRC_URI[sha256sum] = "c14ba9ddcb0055522073477b8fd8bf1ddf5d219e75fdfd4699b7e0ce5350d6b0"
Best Regards,
Maxin
prev parent reply other threads:[~2016-01-05 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 14:08 [PATCH 1/2] bluez5: upgrade to 5.37 Maxin B. John
2016-01-05 14:08 ` [PATCH 2/2] connman: upgrade to 1.31 Maxin B. John
2016-01-05 20:29 ` Burton, Ross
2016-01-05 15:01 ` [PATCH 1/2] bluez5: upgrade to 5.37 Martin Jansa
2016-01-05 15:21 ` Maxin B. John [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=20160105152157.GA31893@mbabyjoh-mobl.fi.intel.com \
--to=maxin.john@intel.com \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox