From: Cyril Bur <cyrilbur@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kvm-unit-tests: Bump version
Date: Tue, 21 Nov 2017 10:27:32 +1100 [thread overview]
Message-ID: <1511220452.6880.2.camel@gmail.com> (raw)
In-Reply-To: <20171120221404.256dc295@windsurf.lan>
On Mon, 2017-11-20 at 22:14 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 20 Nov 2017 16:48:40 +1100, Cyril Bur wrote:
> > Since binutils commit 1a9ccd70f9a7 ("Fix the linker so that it will not
> > silently generate ELF binaries with invalid program headers. Fix readelf
> > to report such invalid binaries.") the behaviour has changed and
> > binutils tries to create a program header segment for which there is no
> > space. Thanks to Nicholas Piggin and his patch to Linux:
> > https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=ff45000fcb56b5b0f
> >
> > Cedric fixed this in kvm-unit-tests commit 95062c20790d ("powerpc: add
> > -n to LDFLAGS") so bump to that version.
> >
> > Fixes:
> > http://autobuild.buildroot.net/results/80825b492abf61313637b109d6a0944b38d5f739
> > Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> > ---
> > package/kvm-unit-tests/kvm-unit-tests.mk | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> I'm not sure how you tested this patch. The change to the hash file was
> missing, and one of the patches in package/kvm-unit-tests/ was not
> applying anymore.
>
> I've fixed up those issues and applied your patch to the master branch,
> but it'd be nice to have a patch tested a bit better next time :-)
>
> Thanks!
>
Yeah sorry, I think I had a really old tree, I use buildroot for so
much I think there was a fail on my part to check the tree. Sorry!
> Thomas
next prev parent reply other threads:[~2017-11-20 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 5:48 [Buildroot] [PATCH] kvm-unit-tests: Bump version Cyril Bur
2017-11-20 8:06 ` Baruch Siach
2017-11-20 21:14 ` Thomas Petazzoni
2017-11-20 23:27 ` Cyril Bur [this message]
2017-11-20 23:25 ` Cyril Bur
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=1511220452.6880.2.camel@gmail.com \
--to=cyrilbur@gmail.com \
--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