From: Mike Snitzer <snitzer@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH] scsi_dh: allow 3rd party multipath drivers to scsi_dh_detach
Date: Thu, 5 Jan 2012 10:24:41 -0500 [thread overview]
Message-ID: <20120105152441.GA5130@redhat.com> (raw)
In-Reply-To: <4EF039D5.5010201@suse.de>
On Tue, Dec 20 2011 at 2:31am -0500,
Hannes Reinecke <hare@suse.de> wrote:
> On 12/15/2011 10:44 PM, Mike Snitzer wrote:
> > Some scsi_dh modules are known to conflict with with 3rd party multipath
> > drivers (e.g. scsi_dh_emc conflicts with EMC PowerPath).
> >
> > Allow 3rd party multipath drivers to programatically detach a scsi_dh
> > using the scsi_dh_detach() interface rather than require writing
> > 'detach' to /sys/block/sdX/queue/dh_state
> >
> > Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> No problem with that.
>
> Acked-by: Hannes Reinecke <hare@suse.de>
Thanks Hannes,
So will this change make it into 3.3? In general, I'm not clear on
where scsi_dh changes are staged for upstream inclusion.
Mike
next prev parent reply other threads:[~2012-01-05 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 21:44 [RFC PATCH] scsi_dh: allow 3rd party multipath drivers to scsi_dh_detach Mike Snitzer
2011-12-20 7:31 ` Hannes Reinecke
2012-01-05 15:24 ` Mike Snitzer [this message]
2012-04-05 14:47 ` Mike Snitzer
2012-04-20 14:45 ` [RESEND][PATCH] [SCSI] scsi_dh: allow 3rd party multipath drivers to use scsi_dh_detach Mike Snitzer
2012-04-20 15:17 ` James Bottomley
2012-04-20 15:46 ` Mike Snitzer
2012-04-20 15:49 ` Chandra Seetharaman
2012-04-20 17:34 ` [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT_SYMBOL Mike Snitzer
2012-04-20 20:41 ` Alan Cox
2012-04-20 21:58 ` Mike Snitzer
2012-04-20 22:20 ` Alan Cox
2012-04-20 22:58 ` Mike Snitzer
2012-04-20 23:14 ` Alan Cox
2012-04-20 23:34 ` Mike Snitzer
2012-04-22 22:13 ` Mike Snitzer
2012-04-22 22:34 ` Alan Cox
2012-04-22 23:01 ` Mike Snitzer
2012-04-22 23:13 ` Alan Cox
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=20120105152441.GA5130@redhat.com \
--to=snitzer@redhat.com \
--cc=hare@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).