From: Robert Yang <liezhi.yang@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 09/15] kexec-tools: update to 2.0.13
Date: Wed, 31 Aug 2016 14:57:27 +0800 [thread overview]
Message-ID: <1e793cfe-71fd-fcea-c86c-86cb916ac939@windriver.com> (raw)
In-Reply-To: <e702a991cf06c5270d3b0c767beee8baa5ed4c36.1472480768.git.alexander.kanavin@linux.intel.com>
Hello,
It seems that this one causes build errors on arm AFAIK:
https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/933/steps/BuildImages/logs/stdio
// Robert
On 08/29/2016 10:30 PM, Alexander Kanavin wrote:
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> .../kexec/{kexec-tools_2.0.12.bb => kexec-tools_2.0.13.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-kernel/kexec/{kexec-tools_2.0.12.bb => kexec-tools_2.0.13.bb} (88%)
>
> diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.13.bb
> similarity index 88%
> rename from meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
> rename to meta/recipes-kernel/kexec/kexec-tools_2.0.13.bb
> index 59376c8..338a7d9 100644
> --- a/meta/recipes-kernel/kexec/kexec-tools_2.0.12.bb
> +++ b/meta/recipes-kernel/kexec/kexec-tools_2.0.13.bb
> @@ -10,8 +10,8 @@ SRC_URI += " \
> file://0001-vmcore-dmesg-Define-_GNU_SOURCE.patch \
> "
>
> -SRC_URI[md5sum] = "10ddaae0e86af54407b164a1f5a39cc3"
> -SRC_URI[sha256sum] = "cc7b60dad0da202004048a6179d8a53606943062dd627a2edba45a8ea3a85135"
> +SRC_URI[md5sum] = "b7595eb4705e482ee6fc1121a5b6131b"
> +SRC_URI[sha256sum] = "70df562d76213e54833228379710ada1afd98a86ee1ce5644eaa68c54e102e25"
>
> PACKAGES =+ "kexec kdump vmcore-dmesg"
>
>
next prev parent reply other threads:[~2016-08-31 6:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 14:30 [PATCH 00/15] Version updates and webkitgtk build race fix Alexander Kanavin
2016-08-29 14:30 ` [PATCH 01/15] libwebp: upgrade to 0.5.1 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 02/15] btrfs-tools: update to 4.7.1 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 03/15] iso-codes: upgrade to 3.69 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 04/15] bash-completion: update to 2.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 05/15] bdwgc: update to 7.6.0 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 06/15] ffmpeg: update to 3.1.2 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 07/15] gobject-introspection: odd versions are development snapshots Alexander Kanavin
2016-08-29 14:30 ` [PATCH 08/15] gnutls: update to 3.5.3 Alexander Kanavin
2016-08-30 22:43 ` Richard Purdie
2016-08-31 8:50 ` [PATCHv2 " Jussi Kukkonen
2016-08-29 14:30 ` [PATCH 09/15] kexec-tools: update to 2.0.13 Alexander Kanavin
2016-08-31 6:57 ` Robert Yang [this message]
2016-08-29 14:30 ` [PATCH 10/15] lighttpd: update to 1.4.41 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 11/15] mpg123: update to 1.23.6 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 12/15] nss: update to 3.25 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 13/15] asciidoc: fix upstream version check Alexander Kanavin
2016-08-29 14:30 ` [PATCH 14/15] webkitgtk: upgrade to 2.12.4 Alexander Kanavin
2016-08-29 14:30 ` [PATCH 15/15] webkitgtk: fix racy double build of WebKit2-4.0.gir Alexander Kanavin
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=1e793cfe-71fd-fcea-c86c-86cb916ac939@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=alexander.kanavin@linux.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