linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/2] Fix a couple hpsa bugs related to device discovery
@ 2010-12-16 19:00 Stephen M. Cameron
  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
  0 siblings, 2 replies; 3+ messages in thread
From: Stephen M. Cameron @ 2010-12-16 19:00 UTC (permalink / raw)
  To: james.bottomley
  Cc: linux-scsi, mike.miller, linux-kernel, thenzl, akpm, smcameron

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-12-16 19:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-16 19:00 [PATCH 0/2] Fix a couple hpsa bugs related to device discovery Stephen M. Cameron
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

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).