From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] move prototype for gunzip() to common.h
Date: Tue, 8 Dec 2009 18:25:55 +0100 [thread overview]
Message-ID: <20091208172555.GF16545@leila.ping.de> (raw)
In-Reply-To: <1260292862-30403-1-git-send-email-w.wegner@astro-kom.de>
Hi,
sorry I did not know where to put additional comments...
I tested this patch for compile-cleanness with a powerpc toolchain
(CodeSourcery freescale-4.4-78-powerpc-linux-gnu-i686-pc-linux-gnu.tar.bz2
to be exact). The warnings and errors were not significantly different
with and without this patch - there is no single board in MAKEALL that
is compiled without warnings using this toolchain, so it was a bit
difficult to compare.
Best regards,
Wolfgang
next prev parent reply other threads:[~2009-12-08 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 17:21 [U-Boot] [PATCH] move prototype for gunzip() to common.h Wolfgang Wegner
2009-12-08 17:25 ` Wolfgang Wegner [this message]
2009-12-08 21:06 ` Wolfgang Denk
2009-12-09 12:46 ` Jerry Van Baren
2009-12-09 13:14 ` Wolfgang Wegner
2009-12-08 21:20 ` Wolfgang Denk
2009-12-09 14:16 ` [U-Boot] [PATCH] move prototypes for gunzip() and zunzip() " Wolfgang Wegner
2009-12-21 20:40 ` Wolfgang Denk
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=20091208172555.GF16545@leila.ping.de \
--to=wolfgang@leila.ping.de \
--cc=u-boot@lists.denx.de \
/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