From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/6] [WIP] Add crostool-NG as backend to generate toolchain
Date: Fri, 14 May 2010 12:11:29 +0200 [thread overview]
Message-ID: <20100514121129.01085a6a@surf> (raw)
In-Reply-To: <20100509230759.16258.48956.stgit@roazhon.bzh.lan>
Hello Yann,
I did a quick review of your patches, and found nothing specific to
say, it looks good to me.
I would at least like patches 1 -> 5 to be merged early in the release
cycle of 2010.08, because I have other changes to make on external
toolchain support that will depend on these. So don't wait for the
CT-NG support to be fully ready to send preliminary patches cleaning up
things that you need for CT-NG integration.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-05-14 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 23:10 [Buildroot] [PATCH 0/6] [WIP] Add crostool-NG as backend to generate toolchain Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 1/6] toolchain: move helper functions from external toolchain Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 2/6] toolchain: rename external toolchain dir Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 3/6] toolchain: move makefile includes Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 4/6] toolchain: move buildroot config files Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 5/6] toolchain: rename base target for external toolchains Yann E. MORIN
2010-05-09 23:11 ` [Buildroot] [PATCH 6/6] toolchain: add new toolchain backend: crosstool-NG Yann E. MORIN
2010-05-14 10:11 ` Thomas Petazzoni [this message]
2010-06-01 7:15 ` [Buildroot] [PATCH 0/6] [WIP] Add crostool-NG as backend to generate toolchain Thomas Petazzoni
2010-06-01 17:55 ` 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=20100514121129.01085a6a@surf \
--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