linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <lsml@rtr.ca>
Cc: Mark Lord <lkml@rtr.ca>, Christoph Hellwig <hch@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] QStor SATA/RAID driver for 2.6.9-rc3
Date: Thu, 07 Oct 2004 16:46:19 -0400	[thread overview]
Message-ID: <4165AB1B.8000204@pobox.com> (raw)
In-Reply-To: <4165A85D.7080704@rtr.ca>

Mark Lord wrote:
> Jeff Garzik wrote:
> 
>> Overall, I don't see why it is so damned difficult to delete the hooks 
>> then add them back when they _are_ needed.  I would certainly support 
>> you in that effort.
> 
> 
> Okay, that can work.
> 
> Except that the hooks ARE needed NOW.
> 
> Right NOW, there is a programmer working on the RAID management
> interface, and he needs those hooks (or something similar)
> to compile and test his code against the driver.

You're the only person in the world that (a) needs these hooks NOW and 
(b) can utilize the hooks NOW, by your own admission ;-)

That's the best reasoning I've heard for why a piece of code _shouldn't_ 
be in the kernel.  And I'm quite certain you are capable of compiling 
and testing the driver with a local patch held back from upstream.

Upstream is for stuff that's either finished, or at least usable...

	Jeff



  reply	other threads:[~2004-10-07 20:46 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 19:11 [PATCH] QStor SATA/RAID driver for 2.6.9-rc3 Mark Lord
2004-10-07 13:42 ` Mark Lord
2004-10-07 14:07   ` Christoph Hellwig
2004-10-07 15:35     ` Mark Lord
2004-10-07 15:50       ` Jeff Garzik
2004-10-07 20:17         ` Mark Lord
2004-10-07 20:30           ` Jeff Garzik
2004-10-07 20:34             ` Mark Lord
2004-10-07 20:46               ` Jeff Garzik [this message]
2004-10-07 20:54                 ` Mark Lord
2004-10-07 21:15                   ` Christoph Hellwig
2004-10-07 22:03                     ` Mark Lord
2004-10-20 15:44                       ` Christoph Hellwig
2004-10-07 23:39                     ` PATCH] " Mark Lord
2004-10-13 18:56                       ` [PATCH] QStor SATA/RAID driver for 2.6.9-rc4 Mark Lord
2004-10-08 13:19                     ` [PATCH] QStor SATA/RAID driver for 2.6.9-rc3 James Bottomley
2004-10-08 15:15                       ` Mark Lord
2004-10-08 15:27                         ` James Bottomley
2004-10-08 15:34                           ` Mark Lord
2004-10-08 15:38                             ` Jeff Garzik
2004-10-08 16:01                             ` James Bottomley
2004-10-12 17:00                               ` Mark Lord
2004-10-12 17:05                                 ` Jeff Garzik
2004-10-12 17:09                                   ` James Bottomley
2004-10-12 17:31                                     ` Jeff Garzik
2004-10-08 15:38                           ` Mark Lord
2004-10-08 15:47                             ` James Bottomley
2004-10-08 15:49                               ` Jeff Garzik
2004-10-12 16:59                               ` Mark Lord
2004-10-12 17:03                                 ` Jeff Garzik
2004-10-12 17:14                                   ` Mark Lord
2004-10-12 17:19                                     ` Jeff Garzik
2004-10-12 17:23                                     ` Jeff Garzik
2004-10-12 17:17                                 ` James Bottomley
2004-10-12 17:22                                   ` Mark Lord
2004-10-12 17:30                                     ` James Bottomley
2004-10-12 17:33                                       ` Mark Lord
2004-10-12 17:42                                         ` Jeff Garzik
2004-10-12 17:51                                           ` Mark Lord
2004-10-12 18:12                                             ` James Bottomley
2004-10-12 18:36                                               ` Mark Lord
2004-10-12 18:25                                             ` driver hacking tips (was Re: [PATCH] QStor SATA/RAID driver for 2.6.9-rc3) Jeff Garzik
2004-10-12 19:18                                               ` Mark Lord
2004-10-12 19:40                                                 ` Jeff Garzik
2004-10-12 17:34                                     ` [PATCH] QStor SATA/RAID driver for 2.6.9-rc3 Jeff Garzik
2004-10-07 20:31           ` Christoph Hellwig
2004-10-07 20:35           ` Jeff Garzik
2004-10-07 21:16 ` Mark Lord
2004-10-07 21:44   ` Jeff Garzik
2004-10-07 21:45   ` Jeff Garzik
2004-10-13 20:04   ` Jeff Garzik
2004-10-13 22:16     ` Mark Lord
2004-10-13 22:41       ` Jeff Garzik
2004-10-13 23:24         ` Mark Lord
2004-10-13 23:39           ` Jeff Garzik
2004-10-14 16:30             ` Mark Lord
2004-10-14 16:37               ` Mark Lord
2004-10-14 16:52               ` [PATCH] Export ata_scsi_simulate() for use by non-libata drivers Mark Lord
2004-10-14 17:04                 ` Jeff Garzik
2004-10-14 18:44                   ` Mark Lord
2004-10-15  5:04                     ` Jeff Garzik
2004-10-15 13:25                       ` John W. Linville
2004-10-15 14:59                         ` Randy.Dunlap
2004-10-15 15:38                           ` 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=4165AB1B.8000204@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=lsml@rtr.ca \
    /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).