From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Florian Fainelli <florian.fainelli@telecomint.eu>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Add rdc321x defconfig file
Date: Mon, 25 Feb 2008 15:12:02 +0200 [thread overview]
Message-ID: <20080225131202.GF32450@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080225125707.GA27202@elte.hu>
On Mon, Feb 25, 2008 at 01:57:07PM +0100, Ingo Molnar wrote:
>
> * Adrian Bunk <bunk@kernel.org> wrote:
>
> > > the existing 32-bit and 64-bit defconfigs should be enough for that.
> > > For better/full coverage, randconfig should be used.
> >
> > The two big problems with randconfigs are:
> > - either you build each .config both with and without your patch or you
> > have to manually check which of the failures are caused by your patch
> > - you require at least an order of magnitude more builds for having the
> > same amount of common configurations covered
> >
> > And any solution that only works on x86 (e.g. based on the expectation
> > that all randconfig configurations normally build) is of zero value
> > for me since x86 is only one out of 23 architectures.
>
> so if an arguably sane testing method "only" works on x86 then the right
> solution is to fix the other architectures to be sanely testable too.
If you want to fix them I won't stop you...
Until they are fixed I'm staying at using the defconfigs.
But then there's still the other problem that at least I simply don't
want to wait two weeks for having the test compiles of a patch finish.
> I've seen architectures that were build-tested for the _first time_ at
> around 2.6.24-rc8...
That can't be true.
Can you name what architectures you think of and why you think noone
tried to compile them before?
> 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
next prev parent reply other threads:[~2008-02-25 13:13 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 [this message]
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
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=20080225131202.GF32450@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®