From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/3] toolchain/external: add MIPS Codescape MTI GNU Linux toolchain
Date: Wed, 20 Jan 2016 11:14:45 +0000 [thread overview]
Message-ID: <569F6C25.9010102@imgtec.com> (raw)
In-Reply-To: <20160120105916.5f86c027@free-electrons.com>
Hi Thomas,
On 20/01/16 09:59, Thomas Petazzoni wrote:
> Vicente,
>
> On Tue, 15 Dec 2015 16:21:24 +0000, Vicente Olivert Riera wrote:
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>> ---
>> Changes v3 -> v4:
>> - Move the changes to helpers.mk into a separate patch.
>
> I've applied patches 2 and 3 to add the two MIPS Codescape toolchains,
> after rebasing on top of master, and removing the version number of the
> Config.in options.
Yeah, the patches were sent when we were supporting different versions
of the same toolchain, so the version number was necessary. But now that
we only support one version of each one is no longer necessary to have
the version number in the name.
Thanks!
Vincent.
>
> Thanks!
>
> Thomas
>
next prev parent reply other threads:[~2016-01-20 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 16:21 [Buildroot] [PATCH v4 1/3] toolchain: allow side by side sysroot directories Vicente Olivert Riera
2015-12-15 16:21 ` [Buildroot] [PATCH v4 2/3] toolchain/external: add MIPS Codescape MTI GNU Linux toolchain Vicente Olivert Riera
2015-12-29 16:38 ` Romain Naour
2016-01-20 9:59 ` Thomas Petazzoni
2016-01-20 11:14 ` Vicente Olivert Riera [this message]
2015-12-15 16:21 ` [Buildroot] [PATCH v4 3/3] toolchain/external: add MIPS Codescape IMG " Vicente Olivert Riera
2015-12-29 16:32 ` [Buildroot] [PATCH v4 1/3] toolchain: allow side by side sysroot directories Romain Naour
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=569F6C25.9010102@imgtec.com \
--to=vincent.riera@imgtec.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