From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] binutils: Allow upstream 2.29 to be chosen for ARC
Date: Wed, 17 Jan 2018 09:16:09 +0000 [thread overview]
Message-ID: <1516180569.3547.2.camel@synopsys.com> (raw)
In-Reply-To: <20180117082557.17026-1-abrodkin@synopsys.com>
Hi gents,
Please disregard this one.
Looks like I need more morning coffee as this was already applied
a couple of months ago but I was looking at a local tree with 2017.11.x checked-out.
So really sorry for the noise!
-Alexey
On Wed, 2018-01-17 at 11:25 +0300, Alexey Brodkin wrote:
> From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
>
> As of today quite a lot of ARC stuff got merged in upsream
> such that we may finally use upstream realease for building
> and even running Linux kernel and rootfs built with vanilla
> binutils.
>
> Essentially upstream release is still a bit behind our
> GitHub-based releases but let's try to use vanilla version
> and if we're lucky enough with just a small set of back-ported patches
> we'll be able to use vanilla release(s) for everything in Buildroot.
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
next prev parent reply other threads:[~2018-01-17 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 8:25 [Buildroot] [PATCH v2] binutils: Allow upstream 2.29 to be chosen for ARC Alexey Brodkin
2018-01-17 9:16 ` Alexey Brodkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-10 16:37 Alexey Brodkin
2017-11-29 22:37 ` 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=1516180569.3547.2.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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.