From: Hannes Reinecke <hare@suse.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <JBottomley@parallels.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi scan: don't fail scans when host is in recovery
Date: Thu, 23 Feb 2012 08:21:39 +0100 [thread overview]
Message-ID: <4F45E903.2010909@suse.de> (raw)
In-Reply-To: <4F4553DC.7000500@cs.wisc.edu>
On 02/22/2012 09:45 PM, Mike Christie wrote:
> On 02/22/2012 03:56 AM, Hannes Reinecke wrote:
>>> ---
>>> include/scsi/scsi_host.h | 3 ++-
>>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/include/scsi/scsi_host.h b/include/scsi/scsi_host.h
>>> index f1f2644..22b7b23 100644
>>> --- a/include/scsi/scsi_host.h
>>> +++ b/include/scsi/scsi_host.h
>>> @@ -791,7 +791,8 @@ static inline struct device *scsi_get_device(struct Scsi_Host *shost)
>>> **/
>>> static inline int scsi_host_scan_allowed(struct Scsi_Host *shost)
>>> {
>>> - return shost->shost_state == SHOST_RUNNING;
>>> + return shost->shost_state == SHOST_RUNNING ||
>>> + shost->shost_state == SHOST_RECOVERY;
>>> }
>>>
>>> extern void scsi_unblock_requests(struct Scsi_Host *);
>>
>> James, ping?
>> Any reason it was not included?
>>
>
> It is merged in git commit 76e4e12ff2b3ef86773989fd897b194eb38016e6.
I must be blind
Sorry for the noise.
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
prev parent reply other threads:[~2012-02-23 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 5:36 [PATCH 1/1] scsi scan: don't fail scans when host is in recovery michaelc
2012-02-22 9:56 ` Hannes Reinecke
2012-02-22 20:45 ` Mike Christie
2012-02-23 7:21 ` Hannes Reinecke [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=4F45E903.2010909@suse.de \
--to=hare@suse.de \
--cc=JBottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.