From: Andi Kleen <ak@muc.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] janitor project: fix gcc 4 warnings
Date: Mon, 20 Dec 2004 08:03:10 +0000 [thread overview]
Message-ID: <20041220080310.GA47521@muc.de> (raw)
In-Reply-To: <20041219190903.GA30192@muc.de>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On Mon, Dec 20, 2004 at 01:13:16AM +0100, Adrian Bunk wrote:
> > You'll see lots of warnings in LOG. Fix them all and submit patches
> > through the usual janitor channels.
>
> What kind of new warnings does gcc 4.0 emit?
http://www.firstfloor.org/~andi/2.6.10rc2-gcc4-warnings.gz has a full
list from i386 allmodconfig (including some errors)
> Altogether, new warnings in gcc 4.0 might be a nice diagnostics for the
> people who are also trying to find bugs using -W, but I don't see urgent
> reasons for fixing them before gcc 4.0 is actually released.
I disagree. It's better to have the kernel already gcc 4 ready when it is
released. And we always ask other people to test mainline kernels, so
it's only fair to test and use other people's mainline code too.
-Andi
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-12-20 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 19:09 [KJ] janitor project: fix gcc 4 warnings Andi Kleen
2004-12-19 19:47 ` Matthew Wilcox
2004-12-19 20:03 ` Andi Kleen
2004-12-19 21:00 ` Tobias Klauser
2004-12-20 0:13 ` Adrian Bunk
2004-12-20 7:10 ` Andi Kleen
2004-12-20 8:03 ` Andi Kleen [this message]
2004-12-20 8:04 ` Andi Kleen
2004-12-20 12:31 ` Arnd Bergmann
2004-12-22 16:44 ` Kovarththanan Rajaratnam
2005-02-07 23:14 ` Randy.Dunlap
2007-02-15 19:34 ` devzero
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=20041220080310.GA47521@muc.de \
--to=ak@muc.de \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.