From: Matthew Wilcox <matthew@wil.cx>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, Vladislav Bolkhovitin <vst@vlnb.net>,
scst-devel@lists.sourceforge.net,
Mike Christie <michaelc@cs.wisc.edu>,
FUJITA Tomonori <tomof@acm.org>
Subject: Re: [PATCH 2.6.25.1] Add scsi_execute_async_fifo()
Date: Fri, 2 May 2008 11:02:44 -0600 [thread overview]
Message-ID: <20080502170244.GI14976@parisc-linux.org> (raw)
In-Reply-To: <e2e108260805020957k2390b151t7fe6beacc9fe8b34@mail.gmail.com>
On Fri, May 02, 2008 at 06:57:10PM +0200, Bart Van Assche wrote:
> Thanks for looking this up. Would it be an acceptable approach if the
> SCST code is modified such that it calls the code inside
> drivers/scsi/scsi_tgt_lib.c whenever this is appropriate ?
You need to talk to Mike and Tomo.
>From my point of view, the most important bit is the target layer <->
driver API. ie the transfer_response() method in the host template.
I'm sure other people have their own preferences though.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-05-02 17:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 14:38 [PATCH 2.6.25.1] Add scsi_execute_async_fifo() Bart Van Assche
2008-05-02 15:33 ` Christoph Hellwig
2008-05-02 15:53 ` Bart Van Assche
2008-05-02 15:55 ` Christoph Hellwig
2008-05-02 16:06 ` Bart Van Assche
2008-05-02 16:16 ` Matthew Wilcox
2008-05-02 16:23 ` Bart Van Assche
2008-05-02 16:30 ` James Bottomley
2008-05-02 16:43 ` Bart Van Assche
2008-05-02 16:49 ` Matthew Wilcox
2008-05-02 16:57 ` Bart Van Assche
2008-05-02 17:02 ` Matthew Wilcox [this message]
2008-05-02 18:21 ` Vladislav Bolkhovitin
2008-05-02 16:18 ` James Bottomley
2008-05-02 16:39 ` Bart Van Assche
2008-05-02 18:09 ` Vladislav Bolkhovitin
2008-05-02 18:17 ` SCSI target subsystem Vladislav Bolkhovitin
2008-05-03 9:41 ` Bart Van Assche
2008-05-03 9:53 ` Matthew Wilcox
2008-05-03 10:39 ` Bart Van Assche
2008-05-03 13:28 ` Matthew Wilcox
2008-05-03 14:48 ` Bart Van Assche
2008-05-04 15:53 ` Bart Van Assche
2008-05-04 11:35 ` Vladislav Bolkhovitin
2008-05-04 15:23 ` Vladislav Bolkhovitin
2008-05-04 11:48 ` [PATCH 2.6.25.1] Add scsi_execute_async_fifo() Vladislav Bolkhovitin
2008-05-04 17:53 ` Boaz Harrosh
2008-05-13 16:48 ` Vladislav Bolkhovitin
2008-05-13 17:35 ` Boaz Harrosh
2008-05-14 15:58 ` [Scst-devel] " Vladislav Bolkhovitin
2008-05-14 16:38 ` Boaz Harrosh
2008-05-14 16:49 ` Vladislav Bolkhovitin
2008-05-04 15:30 ` Bart Van Assche
2008-05-08 15:02 ` Bart Van Assche
2008-05-08 15:54 ` [Scst-devel] " Arne Redlich
2008-05-13 16:47 ` Vladislav Bolkhovitin
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=20080502170244.GI14976@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bart.vanassche@gmail.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=scst-devel@lists.sourceforge.net \
--cc=tomof@acm.org \
--cc=vst@vlnb.net \
/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).