From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Willem Riede <osst@riede.org>, Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org
Subject: Re: osst changes required to move forward to block request
Date: Tue, 07 Mar 2006 15:53:37 -0600 [thread overview]
Message-ID: <1141768417.3239.52.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060307115913.GA30421@infradead.org>
On Tue, 2006-03-07 at 11:59 +0000, Christoph Hellwig wrote:
> James, could you put this into the scsi-misc tree so we don't have any ULD
> using the scsi_request APIs anymore?
OK, done ... now could someone actually test it?
James
next prev parent reply other threads:[~2006-03-07 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 13:19 osst changes required to move forward to block request Christoph Hellwig
2006-02-07 1:02 ` Willem Riede
2006-02-07 9:12 ` Christoph Hellwig
2006-02-11 19:46 ` Willem Riede
2006-02-14 19:24 ` Christoph Hellwig
2006-02-19 20:27 ` Willem Riede
2006-03-07 11:59 ` Christoph Hellwig
2006-03-07 21:53 ` James Bottomley [this message]
2006-03-07 22:16 ` Willem Riede
2006-03-07 22:43 ` Christoph Hellwig
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=1141768417.3239.52.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@riede.org \
/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