public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>
To: james.bottomley@hansenpartnership.com
Cc: linux-scsi@vger.kernel.org, mike.miller@hp.com,
	linux-kernel@vger.kernel.org, thenzl@redhat.com,
	akpm@linux-foundation.org, smcameron@yahoo.com
Subject: [PATCH 0/2] Fix a couple hpsa bugs related to device discovery
Date: Thu, 16 Dec 2010 13:00:51 -0600	[thread overview]
Message-ID: <20101216185823.545.99641.stgit@beardog.cce.hp.com> (raw)

This series fixes a couple of bugs related to discovering changes to
devices.  1) We should not consider a firmware change to mean the
device identity has changed.  Just because a logical drive's firmware
changes doesn't mean it's not the same drive with the same data, so
it should not be removed and re-added to the scsi mid layer.
2) Likewise if the RAID level is observed to change.  This can happen
for instance by doing a RAID level migration from with the Array
Configuration Utility. 

---

Stephen M. Cameron (2):
      hpsa: do not consider firmware revision when looking for device changes.
      hpsa: do not consider RAID level to be part of device identity


 drivers/scsi/hpsa.c |   11 -----------
 drivers/scsi/hpsa.h |    1 -
 2 files changed, 0 insertions(+), 12 deletions(-)

-- 
-- steve

             reply	other threads:[~2010-12-16 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 19:00 Stephen M. Cameron [this message]
2010-12-16 19:00 ` [PATCH 1/2] hpsa: do not consider firmware revision when looking for device changes Stephen M. Cameron
2010-12-16 19:01 ` [PATCH 2/2] hpsa: do not consider RAID level to be part of device identity Stephen M. Cameron

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=20101216185823.545.99641.stgit@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=smcameron@yahoo.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