From: Dave Jones <davej@codemonkey.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: niteowl@intrinsity.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 kernel bugs
Date: Thu, 6 Feb 2003 22:49:00 +0000 [thread overview]
Message-ID: <20030206224900.GA15328@codemonkey.org.uk> (raw)
In-Reply-To: <20030206131640.2e668374.akpm@digeo.com>
On Thu, Feb 06, 2003 at 01:16:40PM -0800, Andrew Morton wrote:
> gcc -W generates ten megabytes of warnings, with a few gems. We really need
> finer-grained control of gcc warnings so that the good ones can be turned on.
> gcc warnings are being redone at present and this might yet happen...
A 'spare time' project of mine is to get -W builds at least 'mostly clean'
The low hanging fruit got fixed up a while back. Most of the remainder
is signed comparison warnings. gcc-3.4 has promoted this warning to
show up in regular builds too, so at some point, either a lot of effort
is going to have to be undertaken to fix those, or we use -Wno-signed-compare
during builds.
> As for the rest well gee. Perhaps we should stick #error's in there to
> flush out some people who can test the fixes.
Just for giggles I did a quick audit of the results of a make
allyesconfig a few weekends ago. The number of drivers we still have
that need updating to new APIs (from tqueue conversions to cli/sti etc)
is quite disturbing. There's a lot of groundwork to be done there
hopefully before we get to a 2.6test phase, or we're going to be
obsoleting boatloads of drivers.
I meant to clean up the output and feed it all into bugzilla.
I'll get around to it sometime..
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-02-06 22:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:43 2.5.59 kernel bugs niteowl
2003-02-06 21:08 ` Martin J. Bligh
2003-02-06 23:16 ` Alan Cox
2003-02-06 22:33 ` Martin J. Bligh
2003-02-06 21:16 ` Andrew Morton
2003-02-06 22:49 ` Dave Jones [this message]
2003-02-06 23:06 ` Randy.Dunlap
2003-02-28 9:14 ` Paul Laufer
2003-02-07 0:14 ` Russell King
2003-02-07 9:23 ` Oleg Drokin
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=20030206224900.GA15328@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=niteowl@intrinsity.com \
/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