public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Miller <mike.miller@hp.com>
To: Tomas Henzl <thenzl@redhat.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Subject: Re: [PATCH] hpsa: add some older controllers to the kdump blacklist
Date: Tue, 14 Feb 2012 11:11:01 -0600	[thread overview]
Message-ID: <4F3A95A5.8040402@hp.com> (raw)
In-Reply-To: <4F3A94EF.50300@redhat.com>

On 02/14/2012 11:07 AM, Tomas Henzl wrote:
> Some other older controllers also do have problems to perform a kdump.
> Adding controllers to this list means that the driver will signal
> this non-ability via a resettable flag correctly.
> The unsupported list was created after a consultation with HP.
>
> Signed-off-by: Tomas Henzl<thenzl@redhat.com>

Acked-by: Mike Miller <mike.miller@hp.com>

>
> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
> index b96962c..faac5a9 100644
> --- a/drivers/scsi/hpsa.c
> +++ b/drivers/scsi/hpsa.c
> @@ -296,11 +296,23 @@ static u32 unresettable_controller[] = {
>   	0x40800E11, /* Smart Array 5i */
>   	0x409C0E11, /* Smart Array 6400 */
>   	0x409D0E11, /* Smart Array 6400 EM */
> +	0x40700E11, /* Smart Array 5300 */
> +	0x40820E11, /* Smart Array 532 */
> +	0x40830E11, /* Smart Array 5312 */
> +	0x409A0E11, /* Smart Array 641 */
> +	0x409B0E11, /* Smart Array 642 */
> +	0x40910E11, /* Smart Array 6i */
>   };
>
>   /* List of controllers which cannot even be soft reset */
>   static u32 soft_unresettable_controller[] = {
>   	0x40800E11, /* Smart Array 5i */
> +	0x40700E11, /* Smart Array 5300 */
> +	0x40820E11, /* Smart Array 532 */
> +	0x40830E11, /* Smart Array 5312 */
> +	0x409A0E11, /* Smart Array 641 */
> +	0x409B0E11, /* Smart Array 642 */
> +	0x40910E11, /* Smart Array 6i */
>   	/* Exclude 640x boards.  These are two pci devices in one slot
>   	 * which share a battery backed cache module.  One controls the
>   	 * cache, the other accesses the cache through the one that controls
>
>


      reply	other threads:[~2012-02-14 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 17:07 [PATCH] hpsa: add some older controllers to the kdump blacklist Tomas Henzl
2012-02-14 17:11 ` Mike Miller [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=4F3A95A5.8040402@hp.com \
    --to=mike.miller@hp.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cce.hp.com \
    --cc=thenzl@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