From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: fix ARCH value for arm64
Date: Fri, 12 Aug 2016 17:12:27 +0300 [thread overview]
Message-ID: <20160812141226.GM845@tarshish> (raw)
In-Reply-To: <CACqcpZBNHJvQQW0+im8m0g+3VvO_A2KMT1cGhvoSE3kzeBTVwA@mail.gmail.com>
Hi Rapha?l,
On Fri, Aug 12, 2016 at 02:52:25PM +0200, Rapha?l Poggi wrote:
> 2016-08-12 14:32 GMT+02:00 Baruch Siach <baruch@tkos.co.il>:
> > On Fri, Aug 12, 2016 at 01:11:26PM +0200, Raphael Poggi wrote:
> >> Signed-off-by: Raphael Poggi <poggi.raph@gmail.com>
[...]
> >> +else ifeq ($$(KERNEL_ARCH), arm64)
> >
> > Redundant space before "arm64".
>
> Oops, will fix it.
>
> > Also, this is only applicable to version v2016.08.0 that adds initial
> > support for aarch64
> > (http://lists.infradead.org/pipermail/barebox/2016-August/027849.html). A user
> > may set BR2_TARGET_BAREBOX_CUSTOM_VERSION to v2016.08.0+, so this may be
> > applicable to Buildroot master.
>
> You mean, test ($$(KERNEL_ARCH), arm64) and also the barebox version ?
No. This patch doesn't break older Barebox versions, AFAICS. I was only
wondering whether it is master stuff, or -next, since we are now post -rc1. I
tend to think this patch is safe for master.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-08-12 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 11:11 [Buildroot] [PATCH] barebox: fix ARCH value for arm64 Raphael Poggi
2016-08-12 12:32 ` Baruch Siach
2016-08-12 12:52 ` Raphaël Poggi
2016-08-12 14:12 ` Baruch Siach [this message]
2016-08-12 14:29 ` Raphaël Poggi
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=20160812141226.GM845@tarshish \
--to=baruch@tkos.co.il \
--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