From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Koen Kooi <koen.kooi@linaro.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] grub: add git version
Date: Sun, 15 Dec 2013 17:37:40 +0000 [thread overview]
Message-ID: <1387129060.8783.1.camel@ted> (raw)
In-Reply-To: <1386775933-14232-1-git-send-email-koen.kooi@linaro.org>
On Wed, 2013-12-11 at 16:32 +0100, Koen Kooi wrote:
> Recently grub git gained support for ARM builds (using u-boot or EFI as first stage loader) and with 2 extra patches we get support for 64-bit ARM as well.
>
> Buildtested for genericarmv7a, genericarmv8 and qemux86. The genericarmv8 build fails in do_package/strip due to a binutils problem.
>
> Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
No objection but should this have a DEFAULT_PREFERENCE = "-1" at least
for the x86 cases since we try and stick to releases where we can...
Cheers,
Richard
next prev parent reply other threads:[~2013-12-15 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:32 [RFC][PATCH] grub: add git version Koen Kooi
2013-12-15 17:37 ` Richard Purdie [this message]
2013-12-21 7:44 ` Koen Kooi
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=1387129060.8783.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen.kooi@linaro.org \
--cc=koen@dominion.thruhere.net \
--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