From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] bluez5: update to 5.40
Date: Mon, 30 May 2016 18:20:23 +0300 [thread overview]
Message-ID: <1464621623-16991-2-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1464621623-16991-1-git-send-email-maxin.john@intel.com>
5.39 -> 5.40
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/recipes-connectivity/bluez5/{bluez5_5.39.bb => bluez5_5.40.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/bluez5/{bluez5_5.39.bb => bluez5_5.40.bb} (89%)
diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.39.bb b/meta/recipes-connectivity/bluez5/bluez5_5.40.bb
similarity index 89%
rename from meta/recipes-connectivity/bluez5/bluez5_5.39.bb
rename to meta/recipes-connectivity/bluez5/bluez5_5.40.bb
index b38d983..1350095 100644
--- a/meta/recipes-connectivity/bluez5/bluez5_5.39.bb
+++ b/meta/recipes-connectivity/bluez5/bluez5_5.40.bb
@@ -2,8 +2,8 @@ require bluez5.inc
REQUIRED_DISTRO_FEATURES = "bluez5"
-SRC_URI[md5sum] = "c0c2b8d1151c7538bf3ae7bfc78aa912"
-SRC_URI[sha256sum] = "21d1bc9150d3576296595217efb98a746b592389d25d5637e8bee5da7272593b"
+SRC_URI[md5sum] = "eb24c0d9eaeb1fb69833f322ec669e8b"
+SRC_URI[sha256sum] = "dada8b812055afcad4546d9966f9a763e4723169e89706e2b240c7b7e998dc27"
# noinst programs in Makefile.tools that are conditional on READLINE
# support
--
2.4.0
next prev parent reply other threads:[~2016-05-30 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 15:20 [PATCH 1/2] libpng: update to 1.6.22 Maxin B. John
2016-05-30 15:20 ` Maxin B. John [this message]
2016-05-31 7:37 ` [PATCH 2/2] bluez5: update to 5.40 Richard Purdie
2016-05-31 10:43 ` Maxin B. John
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=1464621623-16991-2-git-send-email-maxin.john@intel.com \
--to=maxin.john@intel.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