public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <axboe@suse.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Ed Lin <ed.lin@promise.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	hch <hch@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
	promise_linux <promise_linux@promise.com>
Subject: Re: [PATCH] Promise 'stex' driver
Date: Thu, 20 Jul 2006 23:52:15 -0400	[thread overview]
Message-ID: <44C04F6F.2000906@garzik.org> (raw)
In-Reply-To: <20060721031855.GA31187@suse.de>

Jens Axboe wrote:
> On Thu, Jul 20 2006, Jeff Garzik wrote:
>> Jens Axboe wrote:
>>> If I thought that it would ever be updated to use block tagging, I would
>>> not care at all. The motivation to add it from the Promise end would be
>>> zero, as it doesn't really bring any immediate improvements for them. So
>>> it would have to be done by someone else, which means me or you. I don't
>>> have the hardware to actually test it, so unless you do and would want
>>> to do it, chances are looking slim :-)
>>>
>>> It's a bit of a chicken and egg problem, unfortunately. The block layer
>>> tagging _should_ be _the_ way to do it, and as such could be labelled a
>>> requirement. I know that's a bit harsh for the Promise folks, but
>>> unfortunately someone has to pay the price...
>> I think it's highly rude to presume that someone who has so-far been 
>> responsive, and responsible, will suddenly not be so.  That is not the 
>> way to encourage vendors to join the Linux process.
>>
>> They set up an alias for Linux maintainer stuff and have been acting 
>> like a maintainer that will stick around.  Why punish them for good 
>> behavior?
>>
> 
> I'm not trying to be rude to annyone, sorry if that is the impression
> you got. I'm just looking at things realistically - the fact is that
> moving to block layer tagging is not something that will benefit
> Promise, so it'd be fairly low on their agenda of things to do. I don't
> mean that in any rude sense, I can completely understand that position.
> Why would you want to change something that works?  Hence it's
> reasonable to assume that eg you or I would eventually have to convert
> it.

Did you read the patch that started this thread?  Promise has already 
demonstrated they are willing to add changes requested by the community, 
on top of an already-working driver.

	Jeff



  reply	other threads:[~2006-07-21  3:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 15:07 [PATCH] Promise 'stex' driver Ed Lin
2006-07-20 21:27 ` Jeff Garzik
2006-07-20 23:55   ` James Bottomley
2006-07-21  0:16     ` Jeff Garzik
2006-07-21  1:07       ` Jens Axboe
2006-07-21  1:25         ` Jeff Garzik
2006-07-21  1:38           ` Jens Axboe
2006-07-21  2:10             ` Jeff Garzik
2006-07-21  2:36               ` Jens Axboe
2006-07-21  3:01                 ` Jeff Garzik
2006-07-21  3:18                   ` Jens Axboe
2006-07-21  3:52                     ` Jeff Garzik [this message]
2006-07-21 12:13                       ` Jens Axboe
2006-07-23 19:45                   ` hch
2006-07-23 20:21                     ` Jeff Garzik
2006-07-23 19:44                 ` hch
2006-07-21  1:06   ` Jens Axboe
     [not found] <NONAMEBFJ3sl3xbYiMC000000d4@nonameb.ptu.promise.com>
2006-07-25  9:26 ` hch
2006-07-26  1:20   ` Alan Cox
2006-07-25 17:30 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-06-10 16:08 Jeff Garzik
2006-06-10 16:10 ` Christoph Hellwig
2006-06-10 16:29   ` James Bottomley
2006-06-10 16:34     ` Christoph Hellwig
2006-06-10 16:50       ` Jeff Garzik
2006-06-10 17:10         ` Christoph Hellwig
2006-06-10 16:30   ` Jeff Garzik
2006-06-10 17:06 ` Christoph Hellwig
2006-06-10 17:37   ` Jeff Garzik
2006-06-10 18:22     ` James Bottomley
2006-06-10 18:43       ` Jeff Garzik
2006-06-10 22:28   ` Jeff Garzik
2006-06-10 17:47 ` Alexey Dobriyan

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=44C04F6F.2000906@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=ed.lin@promise.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=promise_linux@promise.com \
    /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