From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: the special workaround for ARC is no longer required
Date: Wed, 23 Nov 2016 23:17:40 +0100 [thread overview]
Message-ID: <20161123231740.5a89afe6@free-electrons.com> (raw)
In-Reply-To: <20161123112016.GA29549@waldemar-brodkorb.de>
Hello,
On Wed, 23 Nov 2016 12:20:16 +0100, Waldemar Brodkorb wrote:
> It seems with the change to gcc 6.x based toolchain this
> workaround is no longer required. Tested with an arc hs toolchain.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/gcc/gcc-initial/gcc-initial.mk | 13 -------------
> 1 file changed, 13 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-23 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 11:20 [Buildroot] [PATCH] gcc: the special workaround for ARC is no longer required Waldemar Brodkorb
2016-11-23 15:50 ` Alexey Brodkin
2016-11-23 22:17 ` Thomas Petazzoni [this message]
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=20161123231740.5a89afe6@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox