mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Florian Fainelli <florian.fainelli@telecomint.eu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Add rdc321x defconfig file
Date: Wed, 27 Feb 2008 08:49:34 +0200	[thread overview]
Message-ID: <20080227064934.GC10603@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080226203053.GB14350@elte.hu>

On Tue, Feb 26, 2008 at 09:30:53PM +0100, Ingo Molnar wrote:
>...
> what would be really useful is an automatic Kconfig tree analysis, with 
> the printing out of too deep dependencies perhaps? Which might result in 
> the breaking down of too deep dependencies - to increase the coverage of 
> randconfig testing. Sometimes the number of "depends on" conditions are 
> mind-blowing.

Sounds like the academic masturbation of trying to find an optimal 
solution to a non-existing problem instead of fixing real issues.

The fact that most testers have a PC plus Toralfs randconfigs has
already catched virtually all compile issues visible on a PC in the 
past during -rc.

If you want to attack real problems then write a script that sends the 
names of all people who signed-off patches touching include/linux/ or 
include/asm-generic/ without having tested the compilation of at least 
the defconfig on all architectures to George W. Bush together with the 
information that these people possess at least as many weapons of mass 
destruction as Saddam Hussein in 2003...

> 	Ingo

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


  reply	other threads:[~2008-02-27  6:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25  9:58 Florian Fainelli
2008-02-25 10:14 ` Ingo Molnar
2008-02-25 10:24   ` Florian Fainelli
2008-02-25 10:51     ` Ingo Molnar
2008-02-25 11:03       ` Florian Fainelli
2008-02-25 11:17       ` Adrian Bunk
2008-02-25 11:27         ` Florian Fainelli
2008-02-25 11:45           ` Adrian Bunk
2008-02-25 11:54             ` Ingo Molnar
2008-02-25 11:08   ` Adrian Bunk
2008-02-25 11:17     ` Ingo Molnar
2008-02-25 11:32       ` Adrian Bunk
2008-02-25 11:50         ` Ingo Molnar
2008-02-25 12:25           ` Adrian Bunk
2008-02-25 12:57             ` Ingo Molnar
2008-02-25 13:12               ` Adrian Bunk
2008-02-25 13:45                 ` Ingo Molnar
2008-02-25 14:09                   ` Adrian Bunk
2008-02-25 19:02       ` Sam Ravnborg
2008-02-26  9:44         ` Ingo Molnar
2008-02-26 20:14           ` Sam Ravnborg
2008-02-26 20:30             ` Ingo Molnar
2008-02-27  6:49               ` Adrian Bunk [this message]
2008-02-27 18:31               ` Sam Ravnborg

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=20080227064934.GC10603@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=florian.fainelli@telecomint.eu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®