Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request v2] Pull request for branch for-2012.02/ext-toolchain-updates
Date: Tue, 31 Jan 2012 23:55:19 +0100	[thread overview]
Message-ID: <20120131235519.6d1f5fa1@skate> (raw)
In-Reply-To: <201201312324.20779.arnout@mind.be>

Le Tue, 31 Jan 2012 23:24:20 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :

>  Didn't you promise to include my "Automatically set -m64 if the 
> architecture is x86_64" patch?  Would you like a repost?

Ah, yes, sorry. Will do.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-01-31 22:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 17:36 [Buildroot] [pull request v2] Pull request for branch for-2012.02/ext-toolchain-updates Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 01/16] Add x86_64 variants to BR2_GCC_TARGET_ARCH Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 02/16] Add the Atom processor in the list of supported x86/x86_64 processors Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 03/16] Improve external toolchain logic to support IA32 Sourcery CodeBench toolchain Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 04/16] Support multilib variants in sub-subdirectories Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 05/16] Expand external toolchain wrapper to custom flags Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 06/16] external-toolchain: remove 2009q1 ARM Sourcery toolchain Thomas Petazzoni
2012-01-28 19:50   ` Yegor Yefremov
2012-01-28 20:54     ` Peter Korsgaard
2012-01-28 21:16     ` Thomas Petazzoni
2012-01-28 23:07       ` Yegor Yefremov
2012-01-28 17:36 ` [Buildroot] [PATCH 07/16] external-toolchain: add Sourcery CodeBench ARM 2011.09 Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 08/16] external-toolchain: bump MIPS 2011.03 from -93 to -110 Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 09/16] external-toolchain: add Sourcery CodeBench PowerPC 2011.03 Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 10/16] external-toolchain: add Sourcery CodeBench x86/x86_64 2011.09 Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 11/16] external-toolchain: Blackfin.uclinux.org 2011R1-RC4 Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 12/16] external-toolchain: details on selecting the multilib variants Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 13/16] external-toolchain: run checks even on extracted toolchains Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 14/16] external-toolchain: adjust check for uClibc static toolchains Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 15/16] external-toolchain: fix description of PowerPC 2010.09 from Mentor Graphics Thomas Petazzoni
2012-01-28 17:36 ` [Buildroot] [PATCH 16/16] external-toolchain: add support for Linaro 2012.01 Thomas Petazzoni
2012-01-31 22:24 ` [Buildroot] [pull request v2] Pull request for branch for-2012.02/ext-toolchain-updates Arnout Vandecappelle
2012-01-31 22:55   ` Thomas Petazzoni [this message]
2012-01-31 22:28 ` Arnout Vandecappelle

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=20120131235519.6d1f5fa1@skate \
    --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