From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: CodeSourcery AMD64 affected by PR19615
Date: Tue, 4 Jul 2017 18:32:34 +0200 [thread overview]
Message-ID: <20170704183234.75a3c811@windsurf> (raw)
In-Reply-To: <20170704120110.29107-1-romain.naour@smile.fr>
Hello,
On Tue, 4 Jul 2017 14:01:09 +0200, Romain Naour wrote:
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
> toolchain/toolchain-common.in | 5 +++++
> .../toolchain-external-codesourcery-amd64/Config.in | 1 +
> 2 files changed, 6 insertions(+)
Both applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-04 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:01 [Buildroot] [PATCH 1/2] toolchain: CodeSourcery AMD64 affected by PR19615 Romain Naour
2017-07-04 12:01 ` [Buildroot] [PATCH 2/2] boot/syslinux: disable syslinux legacy-BIOS for toolchains affected by binutils bug 19615 Romain Naour
2017-07-19 12:52 ` Peter Korsgaard
2017-07-04 16:32 ` Thomas Petazzoni [this message]
2017-07-19 12:49 ` [Buildroot] [PATCH 1/2] toolchain: CodeSourcery AMD64 affected by PR19615 Peter Korsgaard
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=20170704183234.75a3c811@windsurf \
--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