From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
Mike Christie <michaelc@cs.wisc.edu>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 1/8] dm-mpath, scsi_dh: don't let dm detach device handlers
Date: Tue, 12 May 2015 10:10:29 +0200 [thread overview]
Message-ID: <20150512081029.GA27168@lst.de> (raw)
In-Reply-To: <5550A5EF.1060904@suse.de>
On Mon, May 11, 2015 at 02:51:59PM +0200, Hannes Reinecke wrote:
> Whitespace error ...
I'll fix it for the next round after I got some reviews in.
next prev parent reply other threads:[~2015-05-12 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 18:40 integrate scsi_dh better into the scsi core V2 Christoph Hellwig
2015-05-10 18:40 ` [PATCH 1/8] dm-mpath, scsi_dh: don't let dm detach device handlers Christoph Hellwig
2015-05-11 12:51 ` Hannes Reinecke
2015-05-12 8:10 ` Christoph Hellwig [this message]
2015-05-10 18:40 ` [PATCH 2/8] dm-mpath, scsi_dh: request scsi_dh modules in scsi_dh, not dm-mpath Christoph Hellwig
2015-05-10 18:40 ` [PATCH 3/8] scsi_dh: move to drivers/scsi Christoph Hellwig
2015-05-10 18:40 ` [PATCH 4/8] scsi_dh: integrate into the core SCSI code Christoph Hellwig
2015-05-10 18:40 ` [PATCH 5/8] scsi_dh: move device matching to the core code Christoph Hellwig
2015-05-10 18:40 ` [PATCH 6/8] scsi_dh: kill struct scsi_dh_data Christoph Hellwig
2015-05-10 18:40 ` [PATCH 7/8] scsi_dh: add a common helper to get a scsi_device from a request_queue Christoph Hellwig
2015-05-10 18:41 ` [PATCH 8/8] scsi_dh: don't allow to detach device handlers at runtime Christoph Hellwig
2015-05-18 17:28 ` integrate scsi_dh better into the scsi core V2 Christoph Hellwig
2015-05-18 17:36 ` Hannes Reinecke
2015-06-19 13:06 ` Hannes Reinecke
2015-06-19 13:17 ` Christoph Hellwig
2015-06-19 13:20 ` Hannes Reinecke
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=20150512081029.GA27168@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michaelc@cs.wisc.edu \
--cc=snitzer@redhat.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