From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Re: [PATCH 3/5] Microblaze: Added Xilinx toolchain options
Date: Tue, 13 Mar 2012 18:34:55 +0100 [thread overview]
Message-ID: <4F5F853F.8040200@relinux.de> (raw)
Am 12.03.2012 23:06, schrieb Thomas Petazzoni:
> Hello,
>
> Le Sun, 11 Mar 2012 17:49:24 +0100,
> Stephan Hoffmann <sho@relinux.de> a ?crit :
>
>> Signed-off-by: Stephan Hoffmann <sho@relinux.de
>>
>> ---
>> toolchain/toolchain-external/Config.in | 5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
>>
> This should be squashed into PATCH 2/5, and it should also be done
> similarly for the big endian MicroBlaze toolchain (unless its uClibc
> configuration has none of those features).
You are right. I will fix this and resend the series of patches tonight.
I do not know anything about the big endian one because I only use the newer
little endian microblaze.
Stephan
> Thomas
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
reply other threads:[~2012-03-13 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F5F853F.8040200@relinux.de \
--to=sho@relinux.de \
--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