From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] bluez5: upgrade to 5.29
Date: Fri, 03 Apr 2015 20:01:02 +0100 [thread overview]
Message-ID: <551EE36E.2050906@communistcode.co.uk> (raw)
In-Reply-To: <1c70c6838a3982473669bd6001a6b1496144aaa6.1428070227.git.cristian.iorga@intel.com>
On 03/04/2015 15:13, Cristian Iorga wrote:
> - Large release with over a month and 475 commits since 5.28;
> - Internal GATT library received lots of updates;
> - Fix for AVCTP key repeat timeout;
> - Added support for the Multi Profile Specification (MPS).
>
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> meta/recipes-connectivity/bluez5/{bluez5_5.28.bb => bluez5_5.29.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-connectivity/bluez5/{bluez5_5.28.bb => bluez5_5.29.bb} (88%)
>
> diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.28.bb b/meta/recipes-connectivity/bluez5/bluez5_5.29.bb
> similarity index 88%
> rename from meta/recipes-connectivity/bluez5/bluez5_5.28.bb
> rename to meta/recipes-connectivity/bluez5/bluez5_5.29.bb
> index e816998..0fe8e7f 100644
> --- a/meta/recipes-connectivity/bluez5/bluez5_5.28.bb
> +++ b/meta/recipes-connectivity/bluez5/bluez5_5.29.bb
> @@ -1,6 +1,6 @@
> require bluez5.inc
> -SRC_URI[md5sum] = "bc20a8285530758c68f6a60e4ca62a15"
> -SRC_URI[sha256sum] = "85bab48f4b47a158739028682c1e09cf30099c8ea9dfe63360055f8e06fc18a9"
> +SRC_URI[md5sum] = "aa9dc91689695a486c78c131cd68673e"
> +SRC_URI[sha256sum] = "df216a6d5ec6133355e5d4ed6b5e7a188a940940d337374e166758513246f0e4"
>
> # noinst programs in Makefile.tools that are conditional on READLINE
> # support
>
5.30 is available now I think
next prev parent reply other threads:[~2015-04-03 19:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 14:13 [PATCH 0/5] Switch to BlueZ 5.x as default Bluetooth stack Cristian Iorga
2015-04-03 14:13 ` [PATCH 1/5] bluez5: upgrade to 5.29 Cristian Iorga
2015-04-03 19:01 ` Jack Mitchell [this message]
2015-04-03 14:13 ` [PATCH 2/5] bluez: remove recipes collection Cristian Iorga
2015-04-03 14:13 ` [PATCH 3/5] maintainers.inc: remove info related to bluez4 Cristian Iorga
2015-04-03 14:13 ` [PATCH 4/5] upstream_tracking.inc: bluez4 removed from oe-core Cristian Iorga
2015-04-03 14:13 ` [PATCH 5/5] bluetooth.bbclass: set bluez5 as the default BT stack Cristian Iorga
2015-04-05 21:40 ` Burton, Ross
2015-04-06 7:31 ` Iorga, Cristian
2015-04-06 12:57 ` Peter A. Bigot
2015-04-06 13:18 ` Otavio Salvador
2015-04-06 14:32 ` Iorga, Cristian
2015-04-06 21:21 ` Peter A. Bigot
2015-04-06 21:39 ` Christopher Larson
2015-04-06 23:41 ` Peter A. Bigot
2015-04-14 13:28 ` Burton, Ross
2015-04-14 15:38 ` Christopher Larson
2015-04-15 15:05 ` Burton, Ross
2015-04-07 10:55 ` Martin Jansa
2015-04-07 11:21 ` Iorga, Cristian
2015-04-07 12:35 ` Martin Jansa
2015-04-07 10:27 ` Tanu Kaskinen
2015-04-07 11:23 ` Iorga, Cristian
2015-04-07 11:41 ` Tanu Kaskinen
2015-04-07 11:51 ` Iorga, Cristian
2015-04-07 12:36 ` Tanu Kaskinen
2015-04-07 12:44 ` Martin Jansa
2015-04-07 12:46 ` Tanu Kaskinen
2015-04-07 13:02 ` Martin Jansa
2015-04-07 20:16 ` Tanu Kaskinen
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=551EE36E.2050906@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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