linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix up riscom8 driver to use work queues instead of task queueing.
Date: Mon, 18 Aug 2003 12:10:17 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308181205150.5929-100000@home.osdl.org> (raw)
In-Reply-To: <20030818195903.G1737@flint.arm.linux.org.uk>


On Mon, 18 Aug 2003, Russell King wrote:
> 
> True.  However, there is the opposite point of view which is equally
> valid.  There aren't many people with the hardware, and the people
> that there are aren't interested in development kernel series, so
> even if we did convert them during 2.7, we wouldn't hear about it
> until 2.8.

Yes. However, what worries me more is that there are people who have the 
hardware, but because the driver won't even compile for them, they just go 
"oh, well, I'll try it again when the _real_ 2.6.0 hits the streets".

Which obviously won't work.

So I'm trying to make sure that all the broken drivers are gotten to a 
working state. Right now, considering how long they've been broken, that 
means "it must compile" so that people can test them. 

The "leave it broken, so that somebody will fix it properly some day" 
approach is a fine one for early development series. But right now I'd 
prefer to see patches to make drivers compile cleanly, even if people 
can't test them on real hardware.

The intersection of people who have the hardware, and people who have the 
time/knowledge to convert a driver, may be empty. Expecially for odd 
hardware. So let's get those drivers compiling, even if we can't test 
them, so that others _can_ test them.

		Linus


  reply	other threads:[~2003-08-18 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200308181806.h7II6K6D014918@hera.kernel.org>
2003-08-18 18:09 ` Fix up riscom8 driver to use work queues instead of task queueing Jeff Garzik
2003-08-18 18:21   ` Linus Torvalds
2003-08-18 18:28     ` Russell King
2003-08-18 18:47       ` Linus Torvalds
2003-08-18 18:59         ` Russell King
2003-08-18 19:10           ` Linus Torvalds [this message]
2003-08-18 18:44     ` Jeff Garzik
2003-08-18 19:12       ` Linus Torvalds
2003-08-18 19:25         ` Jeff Garzik
2003-08-18 19:36           ` Linus Torvalds
2003-08-18 20:32             ` Andrew Morton
2003-08-18 21:24               ` Jeff Garzik

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=Pine.LNX.4.44.0308181205150.5929-100000@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).