From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/5] ofono: upgrade to 1.19
Date: Mon, 21 Nov 2016 14:22:49 +0200 [thread overview]
Message-ID: <1479730971-23120-3-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1479730971-23120-1-git-send-email-maxin.john@intel.com>
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/recipes-connectivity/ofono/{ofono_1.18.bb => ofono_1.19.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/ofono/{ofono_1.18.bb => ofono_1.19.bb} (52%)
diff --git a/meta/recipes-connectivity/ofono/ofono_1.18.bb b/meta/recipes-connectivity/ofono/ofono_1.19.bb
similarity index 52%
rename from meta/recipes-connectivity/ofono/ofono_1.18.bb
rename to meta/recipes-connectivity/ofono/ofono_1.19.bb
index b070731..adebd71 100644
--- a/meta/recipes-connectivity/ofono/ofono_1.18.bb
+++ b/meta/recipes-connectivity/ofono/ofono_1.19.bb
@@ -4,7 +4,7 @@ SRC_URI = "\
${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
file://ofono \
"
-SRC_URI[md5sum] = "0a6b37c8ace891cb2a7ca5d121043a0a"
-SRC_URI[sha256sum] = "53cdbf342913f46bce4827241c60e24255a3d43a94945edf77482ae5b312d51f"
+SRC_URI[md5sum] = "a5f8803ace110511b6ff5a2b39782e8b"
+SRC_URI[sha256sum] = "a0e09bdd8b53b8d2e4b54f1863ecd9aebe4786477a6cbf8f655496e8edb31c81"
CFLAGS_append_libc-uclibc = " -D_GNU_SOURCE"
--
2.4.0
next prev parent reply other threads:[~2016-11-21 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:22 [PATCH 1/5] bluez5: upgrade to 5.43 Maxin B. John
2016-11-21 12:22 ` [PATCH 2/5] harfbuzz: upgrade to 1.3.3 Maxin B. John
2016-11-21 12:22 ` Maxin B. John [this message]
2016-11-21 12:43 ` [PATCH 3/5] ofono: upgrade to 1.19 André Draszik
2016-11-21 12:22 ` [PATCH 4/5] iw: upgrade to 4.9 Maxin B. John
2016-11-21 12:22 ` [PATCH 5/5] libsolv: upgrade to 0.6.24 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=1479730971-23120-3-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