From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] connman: upgrade to 1.31
Date: Tue, 5 Jan 2016 16:08:14 +0200 [thread overview]
Message-ID: <1452002894-10301-2-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1452002894-10301-1-git-send-email-maxin.john@intel.com>
1.30 -> 1.31
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
.../recipes-connectivity/connman/{connman_1.30.bb => connman_1.31.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/connman/{connman_1.30.bb => connman_1.31.bb} (77%)
diff --git a/meta/recipes-connectivity/connman/connman_1.30.bb b/meta/recipes-connectivity/connman/connman_1.31.bb
similarity index 77%
rename from meta/recipes-connectivity/connman/connman_1.30.bb
rename to meta/recipes-connectivity/connman/connman_1.31.bb
index 7d65ac9..7b6bcfb 100644
--- a/meta/recipes-connectivity/connman/connman_1.30.bb
+++ b/meta/recipes-connectivity/connman/connman_1.31.bb
@@ -7,8 +7,8 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
file://0003-Fix-header-inclusions-for-musl.patch \
file://connman \
"
-SRC_URI[md5sum] = "4a3efdbd6796922db9c6f66da57887fa"
-SRC_URI[sha256sum] = "5c5e464bacc9c27ed4e7269fb9b5059f07947f5be26433b59212133663ffa991"
+SRC_URI[md5sum] = "cb1c413fcc4f49430294bbd7a92f5f3c"
+SRC_URI[sha256sum] = "88fcf0b6df334796b90e2fd2e434d6f5b36cd6f13b886a119b8c90276b72b8e2"
RRECOMMENDS_${PN} = "connman-conf"
--
2.4.0
next prev parent reply other threads:[~2016-01-05 14:06 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 ` Maxin B. John [this message]
2016-01-05 20:29 ` [PATCH 2/2] connman: upgrade to 1.31 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
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=1452002894-10301-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