mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, "Andrew Morton" <akpm@osdl.org>
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Thu, 2 Mar 2006 21:25:06 +0100	[thread overview]
Message-ID: <9a8748490603021225s570bbaa4xc260061398eeea7e@mail.gmail.com> (raw)
In-Reply-To: <20060226224300.GA8835@mars.ravnborg.org>

On 2/26/06, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Sun, Feb 26, 2006 at 05:21:17PM +0100, Jesper Juhl wrote:
> >
> > Hi everyone,
> >
> > I just sat down and build 100 kernels (2.6.16-rc4-mm2 kernels to be exact)
> >
> >       95 kernels were build with 'make randconfig'.
> >       1 kernel was build with the config I normally use for my own box.
> >       1 kernel was build from 'make defconfig'.
> >       1 kernel was build from 'make allmodconfig'.
> >       1 kernel was build from 'make allnoconfig'.
> >       1 kernel was build from 'make allyesconfig'.
> >
> > That was an interresting experience.
> >
> > First of all not very many of the kernels actually build correctly and
> > secondly, if I grep the build logs for warnings I'm swamped.
> >
> > Out of 100 kernels 82 failed to build - that's an 18% success rate people,
> > not very impressive.
> I would recommed to fix the obvious cases and leave it.
> Better to concentrate on 'normal' configs. This includes
> allmodconfig/allyesconfig/defconfig but it certainly does not include a
> bunch of random configs. Real peoples config is much better for this.
>
Thank you for your input.

I agree that "common configs" are the most important ones, but I also
feel that problems need to be fixed in general no matter how "corner
case" or "trivial" or "uncommon" they may be.

I ran an experiment, I reported the results. And from the comments in
this thread and what I've also recieved privately I think I achieved
my goal of getting more bugs fixed :)
I personally fixed some of the warnings.
Other people fixed other warnings and errors as a result of my post.
People got thinking about these things.

All in all I think that's a good result :-)


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      reply	other threads:[~2006-03-02 20:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-26 16:21 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
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 [this message]

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=9a8748490603021225s570bbaa4xc260061398eeea7e@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®