From: Roland Dreier <rdreier@cisco.com>
To: Dave C Boutcher <boutcher@cs.umn.edu>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Jeff Garzik <jeff@garzik.org>,
Arjan van de Ven <arjan@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Anthony Liguori <aliguori@us.ibm.com>,
Chris Wright <chrisw@sous-sol.org>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org, Ian Pratt <ian.pratt@xensource.com>,
ian.pratt@cl.cam.ac.uk,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Date: Fri, 24 Mar 2006 16:47:26 -0800 [thread overview]
Message-ID: <adaveu3fizl.fsf@cisco.com> (raw)
In-Reply-To: <17444.18012.796603.193315@hound.rchland.ibm.com> (Dave C. Boutcher's message of "Fri, 24 Mar 2006 13:19:56 -0600")
Dave> And yeah, I'm aware that there is another SRP implementation
Dave> in the kernel...Merging would be good...
Changing the ibmvscsi driver to use the include/scsi/srp.h header file
at least is on my list of things to do. Probably a 2.6.18 type of thing.
- R.
next prev parent reply other threads:[~2006-03-25 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A95E2296287EAD4EB592B5DEEFCE0E9D4B9E8A@liverpoolst.ad.cl.cam.ac.uk>
2006-03-22 23:09 ` [RFC PATCH 35/35] Add Xen virtual block device driver Jeff Garzik
2006-03-24 12:17 ` Alan Cox
2006-03-24 12:38 ` Jeff Garzik
2006-03-24 13:37 ` Jeff Garzik
2006-03-24 13:40 ` Arjan van de Ven
2006-03-24 13:50 ` Jeff Garzik
2006-03-24 15:33 ` Dave C Boutcher
2006-03-24 19:04 ` Mike Christie
2006-03-24 19:19 ` Dave C Boutcher
2006-03-25 0:32 ` FUJITA Tomonori
2006-03-25 0:47 ` Roland Dreier [this message]
2006-03-24 15:55 ` Alan Cox
2006-03-25 10:03 ` Rusty Russell
2006-03-27 10:14 ` Peter Chubb
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=adaveu3fizl.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aliguori@us.ibm.com \
--cc=arjan@infradead.org \
--cc=boutcher@cs.umn.edu \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=ian.pratt@xensource.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=michaelc@cs.wisc.edu \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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