From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] arch/bfin: internal backend not suitable for some cores
Date: Sat, 2 Sep 2017 21:48:12 +0200 [thread overview]
Message-ID: <20170902214812.70fc882f@windsurf.lan> (raw)
In-Reply-To: <fd7e5dc963d17a2a1c33f575fbf73ab1140099f2.1504381100.git.yann.morin.1998@free.fr>
Hello,
On Sat, 2 Sep 2017 21:38:51 +0200, Yann E. MORIN wrote:
> diff --git a/arch/Config.in.bfin b/arch/Config.in.bfin
> index 90e4ab97b0..8c1c80ad52 100644
> --- a/arch/Config.in.bfin
> +++ b/arch/Config.in.bfin
> @@ -6,12 +6,16 @@ choice
> Specify target CPU
> config BR2_bf606
> bool "bf606"
> + select BR2_ARCH_NOT_UPSTREAM_GCC
Where is this symbol introduced?
Seems like there is some issue in your patch series.
Also, as said in my review of PATCH 1/4, perhaps we should simply drop
those Blackfin variants ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-02 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 19:38 [Buildroot] [PATCH 0/4] arch: not all have support in the internal backend Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 1/4] arch: add option to disable internal toolchain backend Yann E. MORIN
2017-09-02 19:47 ` Thomas Petazzoni
2017-09-02 20:10 ` Yann E. MORIN
2017-09-02 20:17 ` Thomas Petazzoni
2017-09-02 19:38 ` [Buildroot] [PATCH 2/4] arch/csky: internal backend not suitable Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 3/4] arch/bfin: internal backend not suitable for some cores Yann E. MORIN
2017-09-02 19:48 ` Thomas Petazzoni [this message]
2017-09-02 20:01 ` Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 4/4] arch/mips: " Yann E. MORIN
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=20170902214812.70fc882f@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.