From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] iproute2: update 4.6.0 -> 4.7.0
Date: Thu, 11 Aug 2016 16:56:43 +0300 [thread overview]
Message-ID: <1470923804-25804-2-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1470923804-25804-1-git-send-email-maxin.john@intel.com>
4.6.0 -> 4.7.0
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
.../iproute2/{iproute2_4.6.0.bb => iproute2_4.7.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/iproute2/{iproute2_4.6.0.bb => iproute2_4.7.0.bb} (71%)
diff --git a/meta/recipes-connectivity/iproute2/iproute2_4.6.0.bb b/meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb
similarity index 71%
rename from meta/recipes-connectivity/iproute2/iproute2_4.6.0.bb
rename to meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb
index 4971937..426f989 100644
--- a/meta/recipes-connectivity/iproute2/iproute2_4.6.0.bb
+++ b/meta/recipes-connectivity/iproute2/iproute2_4.7.0.bb
@@ -5,8 +5,8 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/net/${BPN}/${BP}.tar.xz \
file://0001-iproute2-de-bash-scripts.patch \
file://iproute2-4.3.0-musl.patch \
"
-SRC_URI[md5sum] = "d015e437e4f744d51d3a1a53341826d5"
-SRC_URI[sha256sum] = "74fc6a8ad085be095a159f8158bbaf385b42af9e101619f233f1ae466829d406"
+SRC_URI[md5sum] = "d4b205830cdc2702f8a0cbd6232129cd"
+SRC_URI[sha256sum] = "8f60dbcfb33a79daae0638f53bdcaa4310c0aa59ae39af8a234020dc69bb7b92"
# CFLAGS are computed in Makefile and reference CCOPTS
#
--
2.4.0
next prev parent reply other threads:[~2016-08-11 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 13:56 [PATCH 1/3] sqlite3: update 3.13.0 -> 3.14.0 Maxin B. John
2016-08-11 13:56 ` Maxin B. John [this message]
2016-08-11 13:56 ` [PATCH 3/3] libpng: update 1.6.23 -> 1.6.24 Maxin B. John
2016-08-11 16:20 ` Burton, Ross
2016-08-12 8:54 ` 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=1470923804-25804-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