From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <jbottomley@parallels.com>,
Robert Elliot <elliot@hp.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi_scan: Send TEST UNIT READY to the LUN before scanning
Date: Sun, 14 Sep 2014 10:17:21 +0200 [thread overview]
Message-ID: <54154F11.4010305@suse.de> (raw)
In-Reply-To: <20140907162406.GA10775@infradead.org>
On 09/07/2014 06:24 PM, Christoph Hellwig wrote:
> Looks like you put a version into the SuSE tree with a blacklist entry
> just for the Fujitsu array that requires the TEST UNIT READY. Can you
> send that version upstream as well?
>
I've just had reports that this is required, as it interferes with
NetApp arrays.
So I'll be reposting a combined series with that.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-14 8:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 7:26 [PATCH 0/2] scanning fixes Hannes Reinecke
2014-06-05 7:26 ` [PATCH 1/2] scsi_scan: Send TEST UNIT READY to the LUN before scanning Hannes Reinecke
2014-06-11 13:40 ` Christoph Hellwig
2014-06-11 14:24 ` James Bottomley
2014-06-11 14:33 ` Hannes Reinecke
2014-06-11 14:46 ` James Bottomley
2014-06-11 15:13 ` Hannes Reinecke
2014-06-11 15:25 ` James Bottomley
2014-06-11 15:04 ` Jeremy Linton
2014-09-07 16:24 ` Christoph Hellwig
2014-09-14 8:17 ` Hannes Reinecke [this message]
2014-06-05 7:26 ` [PATCH 2/2] scsi: Handle power-on reset unit attention Hannes Reinecke
2014-06-11 12:49 ` Christoph Hellwig
2014-06-11 14:19 ` Ewan Milne
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=54154F11.4010305@suse.de \
--to=hare@suse.de \
--cc=elliot@hp.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.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;
as well as URLs for NNTP newsgroup(s).