From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Adrian Bunk <bunk@kernel.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: Tue, 26 Feb 2008 21:14:42 +0100 [thread overview]
Message-ID: <20080226201442.GB32685@uranus.ravnborg.org> (raw)
In-Reply-To: <20080226094451.GL9857@elte.hu>
On Tue, Feb 26, 2008 at 10:44:51AM +0100, Ingo Molnar wrote:
> >
> > It is a simple equation: 10 additional defconfigs can give you more
> > build coverage by additional people. Is it worth it?
>
> i dont think it's worth it on x86, because it has no real meaning so it
> will just be an arbitrary thing that deteriorates over time.
OK
> Subarchitectures on x86 are just a shortcut for the "0.1% of systems
> that were lazy to be properly abstracted into the general PC code". We
> are discouraging additional subarches and the one that got added
> recently will go away soon. The rest is legacy.
So you say we would waste our time doing build test of the legacy
sub-archs. OK.
>
> Really, we should concentrate our testing to where our _testers_ are and
> where our developers are.
>
> And according to lkml, http://kerneloops.org and a 300,000+ sample
> http://smolt.fedoraproject.org/static/stats/stats.html statistics, our
> testers are distributed like this:
>
> - more than 90% of all kernel developers use general PC hardware
>
> - more than 95% of our active testers use general PC hardware
>
> - more than 99.1% of our distro users that are willing to send us
> feedback use general PC hardware as well
>
So I will try to concentrate more on non-PC stuff from now on to
increase the developer and tester base there. Seems we have plenty
of developers and testers to hack and test PC stuff.
> (In that aspect i dont count the million(s?) of non-x86 Linux based
> phones as "a million users", unless they become an active part of our
> ecosystem and do things like hook into kerneloops.org. It's that simple,
> really.)
The "everything on lkml argument"...
At my current company I cannot name a single person that I think
would be able to follow lkml - sorry!
Sam
next prev parent reply other threads:[~2008-02-26 20:14 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 [this message]
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=20080226201442.GB32685@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=florian.fainelli@telecomint.eu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®