public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 00/13] convert voyager over to the x86 quirks model
Date: Wed, 11 Mar 2009 18:53:48 +0000	[thread overview]
Message-ID: <1236797629.3270.67.camel@localhost.localdomain> (raw)
In-Reply-To: <49B7F42C.40006@zytor.com>

On Wed, 2009-03-11 at 10:26 -0700, H. Peter Anvin wrote:
> James Bottomley wrote:
> > 
> > That goes for a huge number of drivers we have in the kernel currently,
> > and several whole architectures, so it's not a barrier to keeping
> > something maintained.
> > 
> >> nobody but you uses development kernels on it,
> > 
> > I don't think we've ever had a problem with a downstream community being
> > supported by a single upstream developer.
> > 
> 
> What "downstream community"?  There is none, and you know it.

There are actually two ... as you've heard me say before.  However,
upstream development is driven by willing maintainers, not by user
popularity contests.

> That is the whole point.  Voyager isn't just a driver -- it's an
> odd-man-out variant of the most used architecture in the world.  If it
> was just a driver, it would make sense.  However, its very existence
> forces constraints on the upstream x86 architecture, and it imposes a
> real and considerable workload on the upstream maintainers -- and that
> is not you, but on us.  When that happens with drivers for obsolete
> hardware, we remove them.

The last I heard from you was that the Subarchitecture infrastructure
was the cause of your increased workload.  Fine, it's gone.  Let me ask
again, what is the *current* problem?  This patch set moves voyager to
the x86_quirks setup as you x86 maintainers requested with the given
reason of reducing your workload.

> Hence, Ingo rather logically asks you to justify this impact on our
> workload.  I would like to know as well.  I'm personally sick of the
> extra overhead this museum piece imposes.

Well, I've already answered your workload above, but given the general
question, there are at least three reasons

     1. It's a currently supported architecture.
     2. It works.
     3. It has a committed maintainer.

It's also important to demonstrate that Linux development is based on
technical merit not personal prejudice.

James



  reply	other threads:[~2009-03-11 18:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-08 16:48 [PATCH 00/13] convert voyager over to the x86 quirks model James Bottomley
2009-03-08 16:48 ` [PATCH 01/13] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops James Bottomley
2009-03-08 16:48   ` [PATCH 02/13] [VOYAGER] x86/mca: make mca_nmi_hook external James Bottomley
2009-03-08 16:48     ` [PATCH 03/13] [VOYAGER] x86: add prefill_possible_map to x86_quirks James Bottomley
2009-03-08 16:48       ` [PATCH 04/13] [VOYAGER] x86: use boot_cpu_id instead of zero for checking boot processor James Bottomley
2009-03-08 16:48         ` [PATCH 05/13] [VOYAGER] x86/voyager: Move voyager detection to a new bootparam area James Bottomley
2009-03-08 16:48           ` [PATCH 06/13] [VOYAGER] x86: eliminate subarchitecture file setup_arch.h James Bottomley
2009-03-08 16:48             ` [PATCH 07/13] [VOYAGER] x86: eliminate subarchitecture file entry_arch.h James Bottomley
2009-03-08 16:48               ` [PATCH 08/13] [VOYAGER] x86: eliminate subarchitecture file do_timer.h James Bottomley
2009-03-08 16:48                 ` [PATCH 09/13] [VOYAGER] x86: redo irq2 cascade setup James Bottomley
2009-03-08 16:48                   ` [PATCH 10/13] [VOYAGER] x86: make disabling the apics functional instead of a flag James Bottomley
2009-03-08 16:48                     ` [PATCH 11/13] [VOYAGER] x86/Voyager: add missing QIC call function single gate James Bottomley
2009-03-08 16:48                       ` [PATCH 12/13] [VOYAGER] x86/Voyager: replace inline io area reads with readX accessors James Bottomley
2009-03-08 16:48                         ` [PATCH 13/13] [VOYAGER] x86/Voyager: Plumb voyager back into the build James Bottomley
2009-03-08 17:15   ` [PATCH 01/13] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops Jeremy Fitzhardinge
2009-03-08 17:23     ` James Bottomley
2009-03-09 20:54 ` [PATCH 00/13] convert voyager over to the x86 quirks model Sam Ravnborg
2009-03-10 21:58 ` Yinghai Lu
2009-03-10 22:02   ` James Bottomley
2009-03-10 22:37 ` Ingo Molnar
2009-03-11 15:41   ` James Bottomley
2009-03-11 17:26     ` H. Peter Anvin
2009-03-11 18:53       ` James Bottomley [this message]
2009-03-11 22:55     ` Ingo Molnar

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=1236797629.3270.67.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=hpa@linux.intel.com \
    --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