From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] elfutils: bump version to 0.160
Date: Tue, 11 Nov 2014 14:12:05 +0100 [thread overview]
Message-ID: <54620B25.4050306@mind.be> (raw)
In-Reply-To: <1415706464-15288-3-git-send-email-Vincent.Riera@imgtec.com>
On 11/11/14 12:47, Vicente Olivert Riera wrote:
> +sha256 741b556863c069ceab2d81eb54aeda8c34f46728859704eaf9baef8503e9a9d1 elfutils-0.160.tar.bz2
> +sha256 feb307acf472598ea7af4e4b439251613a8f5d81e804b4abf9aeca195a5d4254 elfutils-portability.patch
Forgot to mention in my previous review: I verified the first hash against the
upstream gpg signature, and I verified the second hash against my local download.
I also did a simple build test. So:
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
[for -next, and if the 0006 patch subject is modified]
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-11-11 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 11:47 [Buildroot] [PATCH v4 0/2] elfutils: version bump Vicente Olivert Riera
2014-11-11 11:47 ` [Buildroot] [PATCH v4 1/2] elfutils: rename patches to follow the new name structure Vicente Olivert Riera
2014-11-13 17:40 ` Yann E. MORIN
2014-11-11 11:47 ` [Buildroot] [PATCH v4 2/2] elfutils: bump version to 0.160 Vicente Olivert Riera
2014-11-11 13:12 ` Arnout Vandecappelle [this message]
2014-11-13 17:45 ` Yann E. MORIN
2014-11-13 19:26 ` Arnout Vandecappelle
2014-11-19 22:01 ` [Buildroot] [PATCH v4 0/2] elfutils: version bump Thomas Petazzoni
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=54620B25.4050306@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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