public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
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 14:45:49 +0100	[thread overview]
Message-ID: <20080225134549.GA4481@elte.hu> (raw)
In-Reply-To: <20080225131202.GF32450@cs181133002.pp.htv.fi>


* Adrian Bunk <bunk@kernel.org> wrote:

> > 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.

As i said it before, it's totally senseless to add zillions of 
defconfigs to x86. The two that are there should be enough for a 
sniff-test - and much more than that has to be done to ensure that a 
patch doesnt break anything. Not even a 100 defconfigs would match 
proper randconfig coverage.

according to one particular arbitrary piece of metrics [1], ~99.15% of 
our testers use x86 - and the oopses collected on kerneloops.org show a 
similar proportion.

> > 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?

sorry, s/build-tested/boot-tested.

there's been only 6 commits to arch/v850 between v2.6.23 and v2.6.24.
None of them seems to suggest that anyone ever tested v850 in the last
year or so.

	Ingo

[1] http://smolt.fedoraproject.org

  reply	other threads:[~2008-02-25 13:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25  9:58 [PATCH] Add rdc321x defconfig file 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 [this message]
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=20080225134549.GA4481@elte.hu \
    --to=mingo@elte.hu \
    --cc=bunk@kernel.org \
    --cc=florian.fainelli@telecomint.eu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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