[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110503194919.5154.78352.stgit@beardog.cce.hp.com>
Date: Tue, 03 May 2011 14:52:48 -0500
From: "Stephen M. Cameron" <scameron@...rdog.cce.hp.com>
To: axboe@...nel.dk
Cc: mikem@...rdog.cce.hp.com, akpm@...ux-foundation.org,
thenzl@...hat.com, linux-kernel@...r.kernel.org,
smcameron@...oo.com
Subject: [PATCH 00/16] cciss: May 3, 2011 updates
The following series mostly contains fixes to improve kdump behavior
and esp. to make older controllers which cannot be hard reset work by
doing a soft reset instead. There are a few patches factoring out
various functionality into individual functions make way for the soft
reset functionality. There is also a bugfix which prevents PCI write
combining from potentially causing commands to get lost.
---
Stephen M. Cameron (16):
cciss: add readl after writel in interrupt mask setting code
cciss: do a better job of detecting controller reset failure
cciss: factor out command pool allocation functions
cciss: factor out scatterlist allocation functions
cciss: factor out irq request code
cciss: fix reply pool and block fetch table memory leaks
cciss: get rid of message related magic numbers
cciss: increase time to wait for board reset to start
cciss: clarify messages around reset behavior
cciss: increase timeouts for post-reset no-ops
cciss: use new doorbell-bit-5 reset method
cciss: do soft reset if hard reset is broken
cciss: remove superfluous sleeps around reset code
cciss: do not attempt PCI power management reset method if we know it won't work.
cciss: do not use bit 2 doorbell reset
cciss: add cciss_tape_cmds module paramter
Documentation/blockdev/cciss.txt | 15 +
drivers/block/cciss.c | 571 ++++++++++++++++++++++++++++++--------
drivers/block/cciss.h | 11 +
drivers/block/cciss_cmd.h | 11 +
drivers/block/cciss_scsi.c | 41 ++-
drivers/block/cciss_scsi.h | 4
6 files changed, 515 insertions(+), 138 deletions(-)
--
-- steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists