From: <mingli.yu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-oe][PATCH 1/4] crash: Upgrade to 7.2.6
Date: Fri, 19 Jul 2019 02:15:36 -0700 [thread overview]
Message-ID: <20190719091539.100373-1-mingli.yu@windriver.com> (raw)
From: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
meta-oe/recipes-kernel/crash/{crash_7.2.5.bb => crash_7.2.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-kernel/crash/{crash_7.2.5.bb => crash_7.2.6.bb} (98%)
diff --git a/meta-oe/recipes-kernel/crash/crash_7.2.5.bb b/meta-oe/recipes-kernel/crash/crash_7.2.6.bb
similarity index 98%
rename from meta-oe/recipes-kernel/crash/crash_7.2.5.bb
rename to meta-oe/recipes-kernel/crash/crash_7.2.6.bb
index e124db19c..a8bfe27da 100644
--- a/meta-oe/recipes-kernel/crash/crash_7.2.5.bb
+++ b/meta-oe/recipes-kernel/crash/crash_7.2.6.bb
@@ -26,7 +26,7 @@ SRC_URI = "git://github.com/crash-utility/${BPN}.git \
file://0002-crash-fix-build-error-unknown-type-name-gdb_fpregset.patch \
file://0003-crash-detect-the-sysroot-s-glibc-header-file.patch \
"
-SRCREV = "c0a2fc9d322cf0c5f569ce54e9201d2f586edb0c"
+SRCREV = "4076ebea6626e3f0a20150602c6ffab999ea5c90"
SRC_URI[gdb.md5sum] = "a9836707337e5f7bf76a009a8904f470"
SRC_URI[gdb.sha256sum] = "8070389a5dcc104eb0be483d582729f98ed4d761ad19cedd3f17b5d2502faa36"
--
2.21.0
next reply other threads:[~2019-07-19 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 9:15 mingli.yu [this message]
2019-07-19 9:15 ` [meta-oe][PATCH 2/4] makedumpfile: Upgrade to 1.6.6 mingli.yu
2019-07-19 9:15 ` [meta-oe][PATCH 3/4] hwloc: Upgrade to 1.11.13 mingli.yu
2019-07-19 9:15 ` [meta-oe][PATCH 4/4] iperf3: Upgrade to 3.7 mingli.yu
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=20190719091539.100373-1-mingli.yu@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-devel@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