From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Cc: James Bottomley <James.Bottomley@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: Re: [PATCH] Always pass result and sense on request completion
Date: Fri, 11 Dec 2009 01:32:48 -0600 [thread overview]
Message-ID: <4B21F5A0.1040008@cs.wisc.edu> (raw)
In-Reply-To: <4B213084.1010200@panasas.com>
Boaz Harrosh wrote:
>
> I agree that the req->errors bits where not understood outside of scsi
> up till now. Is multipath only compatible over scsi block devices?
>
It works with any device that has a request_queue and implements
queueing functions like the request_fn. It should work with DASD I think.
prev parent reply other threads:[~2009-12-11 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 12:24 [PATCH] Always pass result and sense on request completion Hannes Reinecke
2009-12-10 9:49 ` Hannes Reinecke
2009-12-10 16:44 ` James Bottomley
2009-12-10 17:03 ` [dm-devel] " Mike Christie
2009-12-10 17:26 ` James Bottomley
2009-12-10 17:31 ` Boaz Harrosh
2009-12-11 7:32 ` Mike Christie [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=4B21F5A0.1040008@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@suse.de \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.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