From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Ed Lin <ed.lin@promise.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"James.Bottomley" <James.Bottomley@SteelEye.com>,
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: Fri, 21 Jul 2006 03:06:22 +0200 [thread overview]
Message-ID: <20060721010622.GA24176@suse.de> (raw)
In-Reply-To: <44BFF539.4000700@garzik.org>
On Thu, Jul 20 2006, Jeff Garzik wrote:
> 5) [agreement/correction] The block tagging API supports adapter-wide
> tags just fine. HOWEVER, I nonetheless feel that block tagging API use
> should be considered post-merge. The 'stex' driver is working and
> tested today. Since _no individual SCSI driver_ uses the block layer
> tagging, it is likely that some instability and core kernel development
> will occur, in order to make that work.
I'd disagree. If the driver gets merged with the current tagging, I'll
get you two beers that it never gets changed.
And you are wrong, block layer tagging is used by at least one SCSI
driver. We definitely need to start pushing it more.
--
Jens Axboe
next prev parent reply other threads:[~2006-07-21 1:06 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
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 [this message]
[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=20060721010622.GA24176@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=ed.lin@promise.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.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