From: Wang Mingyu <wangmy@cn.fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] kexec-tools: upgrade 2.0.19 -> 2.0.20
Date: Fri, 22 Nov 2019 02:51:38 -0800 [thread overview]
Message-ID: <1574419898-23699-2-git-send-email-wangmy@cn.fujitsu.com> (raw)
In-Reply-To: <1574419898-23699-1-git-send-email-wangmy@cn.fujitsu.com>
---
.../kexec/{kexec-tools_2.0.19.bb => kexec-tools_2.0.20.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/kexec/{kexec-tools_2.0.19.bb => kexec-tools_2.0.20.bb} (95%)
diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.19.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.20.bb
similarity index 95%
rename from meta/recipes-kernel/kexec/kexec-tools_2.0.19.bb
rename to meta/recipes-kernel/kexec/kexec-tools_2.0.20.bb
index c3f7435..b79e33b 100644
--- a/meta/recipes-kernel/kexec/kexec-tools_2.0.19.bb
+++ b/meta/recipes-kernel/kexec/kexec-tools_2.0.20.bb
@@ -21,8 +21,8 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/kernel/kexec/kexec-tools-${PV}.tar.gz
file://0006-kexec-arm-undefine-__NR_kexec_file_load-for-arm.patch \
"
-SRC_URI[md5sum] = "052458f0a35c2a3b0d2302caa3318e9f"
-SRC_URI[sha256sum] = "913c8dee918e5855a4ba60d609371390978144b4c8d15d6446ca0057b7bc5e58"
+SRC_URI[md5sum] = "46724b67f32501c5d3e778161347cad9"
+SRC_URI[sha256sum] = "cb16d79818e0c9de3bb3e33ede5677c34a1d28c646379c7ab44e0faa3eb57a16"
inherit autotools update-rc.d systemd
--
2.7.4
next prev parent reply other threads:[~2019-11-22 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 10:51 [PATCH] cronie:upgrade 1.5.4 -> 1.5.5 Wang Mingyu
2019-11-22 3:51 ` Mittal, Anuj
2019-11-22 4:02 ` ✗ patchtest: failure for " Patchwork
2019-11-22 4:02 ` ✗ patchtest: failure for cronie:upgrade 1.5.4 -> 1.5.5 (rev2) Patchwork
2019-11-22 10:51 ` Wang Mingyu [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-31 8:25 [PATCH] kexec-tools:upgrade 2.0.19 -> 2.0.20 Zang Ruochen
2019-07-31 14:08 ` Richard Purdie
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=1574419898-23699-2-git-send-email-wangmy@cn.fujitsu.com \
--to=wangmy@cn.fujitsu.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