Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] arch/arm: restrict more armv8a cores to aarch64
Date: Fri, 18 Jan 2019 15:55:27 +0100	[thread overview]
Message-ID: <87bm4e3ti8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <891faf01bce122d52613f7fc831f32526beaa1a3.1546179362.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sun, 30 Dec 2018 15:16:11 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Since gcc-8, falkor and qdf24xx have been available only as AArch64.
 > Although we could support building in 32-bit for older gcc versions, we
 > decided not to, in the sake of simplicity.

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2018.02.x and 2018.11.x, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2019-01-18 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30 14:16 [Buildroot] [PATCH 0/4] arch/arm: add more cores (branch yem/aarch64-new-cores) Yann E. MORIN
2018-12-30 14:16 ` [Buildroot] [PATCH 1/4] arch/arm: drop useless conditional dependencies for 64-bit-only cores Yann E. MORIN
2018-12-30 14:29   ` Thomas Petazzoni
2018-12-30 14:16 ` [Buildroot] [PATCH 2/4] arch/arm: restrict more armv8a cores to aarch64 Yann E. MORIN
2018-12-30 15:11   ` Thomas Petazzoni
2019-01-18 14:55   ` Peter Korsgaard [this message]
2018-12-30 14:16 ` [Buildroot] [PATCH 3/4] arch/arm: add armv8.2a cortex-based cores Yann E. MORIN
2018-12-30 15:11   ` Thomas Petazzoni
2018-12-30 14:16 ` [Buildroot] [PATCH 4/4] arch/arm: add an armv8.3a core Yann E. MORIN
2018-12-30 15:11   ` 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=87bm4e3ti8.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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