From: James Smart <James.Smart@Emulex.Com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Benny Halevy <bhalevy@panasas.com>,
linux-scsi@vger.kernel.org, Mike Christie <mchristi@redhat.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
Jens Axboe <jens.axboe@oracle.com>, Dalit Naor <DALIT@il.ibm.com>,
Liran Schour <LIRANS@il.ibm.com>,
Sami.Iren@seagate.com, Daniel.E.Messinger@seagate.com,
stuart.brodsky@seagate.com, open-iscsi@googlegroups.com,
Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [RFC] support for bidirectional transfers and variable length CDBs
Date: Mon, 30 Oct 2006 07:55:25 -0500 [thread overview]
Message-ID: <4545F63D.7080504@emulex.com> (raw)
In-Reply-To: <20061029134852.GB22902@infradead.org>
Christoph Hellwig wrote:
>>> - you submit your patch that fixes the scsi_execute comment typo
>>> - you submit your patch to add the VARLEN_CDB opcode
>>> - you start converting as many as possible drivers to the
>>> above wrapper API (I already had a big FC card vendor signed up
>>> for this, but no updates so far..)
Sign me (Emulex) up for the last item - and if you send me pre-releases
of your patches, we can help out with preliminary testing.
-- james s
next prev parent reply other threads:[~2006-10-30 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4541F822.70700@panasas.com>
2006-10-28 16:36 ` [RFC] support for bidirectional transfers and variable length CDBs Christoph Hellwig
2006-10-29 13:33 ` Benny Halevy
2006-10-29 13:48 ` Christoph Hellwig
2006-10-30 12:55 ` James Smart [this message]
2006-10-29 19:30 ` Matthew Wilcox
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=4545F63D.7080504@emulex.com \
--to=james.smart@emulex.com \
--cc=DALIT@il.ibm.com \
--cc=Daniel.E.Messinger@seagate.com \
--cc=James.Bottomley@SteelEye.com \
--cc=LIRANS@il.ibm.com \
--cc=Sami.Iren@seagate.com \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=open-iscsi@googlegroups.com \
--cc=stuart.brodsky@seagate.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.