From: Christoph Hellwig <hch@infradead.org>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH RFC/RFT 2/4] add scsi helpers
Date: Thu, 15 Sep 2005 19:29:39 +0100 [thread overview]
Message-ID: <20050915182939.GA1316@infradead.org> (raw)
In-Reply-To: <4329B586.6010802@cs.wisc.edu>
On Thu, Sep 15, 2005 at 12:55:18PM -0500, Mike Christie wrote:
> Actually after talking with Jens, I think it is better to keep the
> function in scsi_lib and move my blk_rq_map_iov() function there. The
> problem is that sg and st have some special needs and as a result do
> some things like partial setup themselves. It looks like nobody wants
> the burdon of having these special case fucntions :) but since SCSI's
> ULDs are the only user and probably will be the only user does it make
> sense to keep them there?
ok, makes sense
prev parent reply other threads:[~2005-09-15 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:19 [PATCH RFC/RFT 2/4] add scsi helpers Mike Christie
2005-09-15 10:13 ` Christoph Hellwig
2005-09-15 17:30 ` Mike Christie
2005-09-15 17:55 ` Mike Christie
2005-09-15 18:29 ` Christoph Hellwig [this message]
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=20050915182939.GA1316@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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