From: Adrian Bunk <bunk@stusta.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Sun, 26 Feb 2006 18:41:23 +0100 [thread overview]
Message-ID: <20060226174123.GJ3674@stusta.de> (raw)
In-Reply-To: <9a8748490602260929v74fd8358r8bdb2d670508bb0a@mail.gmail.com>
On Sun, Feb 26, 2006 at 06:29:54PM +0100, Jesper Juhl wrote:
> On 2/26/06, Adrian Bunk <bunk@stusta.de> wrote:
>...
> > > >From 100 kernel builds there was a total of 16152 warnings and 645 of those
> > > are unique warnings, the rest are duplicates.
> > >
> > > We are drowning in warnings people. Sure, many of the warnings are due to
> > > gcc getting something wrong and shouldn't really be emitted, but a lot of
> > > them point to actual problems or deficiencies (I obviously haven't looked
> > > at them all in detail yet, so take that with a grain of salt please).
> > >...
> >
> > It's well-known that BROKEN_ON_SMP drivers often spit 50 warnings in one
> > warning. If you remove the dozen worst drivers the numbers should look
> > much better.
> >
> Better yet, let's fix the warnings.
It's never bad if someone converts drivers still using cli/sti.
Unfortunately, this is non-trivial...
> > Not that our current situation was perfect, but the number of warnings
> > in .config's people usually use isn't that bad.
>
> I agree it's not too bad for most people. The point of my post was
> mostly a "call to arms" trying to get people interrested in fixing all
> the warnings and build errors we have.
I'm agreeing that this is a good idea, I simply disagreed with your
"we suck at..." point, since although we can become better we aren't
that bad.
> There's a lot of focus on implementing new features - and that's great
> - but there's little emphasis on fixing the problems we have and
> already know about - I'd like to see that change, and my post was
> mainly an attempt at making that happen :)
IMHO, the real problems we already know about are not warnings, they are
the ones listed at
http://bugzilla.kernel.org/
And in these cases, the bugs in unmaintained areas of the kernel like
APM or the floppy driver are the worst ones.
> Jesper Juhl <jesper.juhl@gmail.com>
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-02-26 17:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 16:21 Building 100 kernels; we suck at dependencies and drown in warnings Jesper Juhl
2006-02-26 16:31 ` Jesper Juhl
2006-02-26 16:35 ` Jesper Juhl
2006-02-26 19:31 ` Dave Jones
2006-02-26 19:43 ` Jesper Juhl
2006-02-26 20:11 ` Jesper Juhl
2006-02-26 23:45 ` Nigel Cunningham
2006-02-27 2:02 ` Pavel Machek
2006-02-26 19:30 ` Dave Jones
2006-02-26 17:00 ` Adrian Bunk
2006-02-26 17:29 ` Jesper Juhl
2006-02-26 17:41 ` Adrian Bunk [this message]
2006-02-26 18:08 ` Jesper Juhl
2006-02-26 17:38 ` Jesper Juhl
2006-02-26 18:21 ` Diego Calleja
2006-02-26 18:45 ` Jesper Juhl
2006-02-26 19:03 ` Diego Calleja
2006-02-26 20:42 ` Lee Revell
2006-02-26 20:44 ` Jesper Juhl
2006-02-26 21:46 ` Nix
2006-02-26 21:49 ` Jesper Juhl
2006-02-26 21:53 ` Lee Revell
2006-02-26 21:56 ` Jesper Juhl
2006-02-26 22:08 ` Lee Revell
2006-02-26 22:12 ` Jesper Juhl
2006-02-27 17:25 ` Stephen Hemminger
2006-02-26 22:14 ` Al Viro
2006-02-26 22:32 ` Nix
2006-02-26 22:50 ` Lee Revell
2006-02-26 21:14 ` Grant Coady
2006-02-27 12:56 ` David Greaves
2006-02-28 10:30 ` Roman Zippel
2006-02-26 22:43 ` Sam Ravnborg
2006-03-02 20:25 ` Jesper Juhl
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=20060226174123.GJ3674@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox