From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v3] toolchain/external: bump Linaro ARM, ARMEB and AArch64 toolchains (branch yem/toolchain-linaro-2015.08)
Date: Tue, 3 Nov 2015 22:11:43 +0100 [thread overview]
Message-ID: <20151103221143.47625aac@free-electrons.com> (raw)
In-Reply-To: <cover.1445903025.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Tue, 27 Oct 2015 00:49:37 +0100, Yann E. MORIN wrote:
> Yann E. MORIN (3):
> toolchain/external: bump Linaro ARM to 2015.08
> toolchain/external: bump Linaro ARMEB to 2015.08
> toolchain/external: bump Linaro AArch64 to 2015.08
All three applied, thanks!
On the first patch, I fixed the s/eglibc/glibc/ typo noticed by Baruch.
On the second patch, I rewrote the Config.in help text, since it was
not referring to the proper Linaro toolchain version (you copy/pasted
from the wrong place it seems).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-03 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 23:49 [Buildroot] [PATCH 0/3 v3] toolchain/external: bump Linaro ARM, ARMEB and AArch64 toolchains (branch yem/toolchain-linaro-2015.08) Yann E. MORIN
2015-10-26 23:49 ` [Buildroot] [PATCH 1/3 v3] toolchain/external: bump Linaro ARM to 2015.08 Yann E. MORIN
2015-10-27 4:33 ` Baruch Siach
2015-10-27 12:52 ` Yann E. MORIN
2015-10-26 23:49 ` [Buildroot] [PATCH 2/3 v3] toolchain/external: bump Linaro ARMEB " Yann E. MORIN
2015-10-26 23:49 ` [Buildroot] [PATCH 3/3 v3] toolchain/external: bump Linaro AArch64 " Yann E. MORIN
2015-11-03 21:11 ` Thomas Petazzoni [this message]
2015-11-03 21:20 ` [Buildroot] [PATCH 0/3 v3] toolchain/external: bump Linaro ARM, ARMEB and AArch64 toolchains (branch yem/toolchain-linaro-2015.08) 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=20151103221143.47625aac@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