That one's my mistake, it made to Linus via my sending patches at linux-scsi
and James. Alan, I saw your megaraid updates after I posted these to l-s,
and was in the process of merging the two, which I didn't finish on Friday.
The megaraid driver, especially in 2.5.x, has been suffering from neglect
from the official maintainer, LSI. Atul has returned from lengthy hiatus,
and claims to be ready to get megaraid back into working shape. I *really*
want Atul to get 2.4.x straightened out as a first priority this week, and
then tackle 2.5.x ASAP thereafter. Ideally for 2.5, after a short
stabilization period for the current 1.18 driver and in parallel a merging
of megaraid2, that the 1.18 driver could be dropped in favor of a cleaner
(and proper error-handling) megaraid 2.00 driver. There's even hope that
some megaraid cards can actually do board resets (not all can), and that
logic could be incorporated into the error handling routines. As it stands
now, they are no-ops once a command had been sent to the card.
-Matt
-- Matt Domsch Sr. Software Engineer, Lead Engineer, Architect Dell Linux Solutions www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/