Skip to content

mpt fusion: Firmware Event implementation using seperate WorkQueue

Kashyap, Desai linux-scsi 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest6 patches 13 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6mpt fusion: fix for previous patch taskmgmt in progress should be cleared before returndrivers/message/fusion/mptsas.c+17 -64 replies
2/6mpt fusion: Firmware Event implementation using seperate WorkQueuedrivers/message/fusion/mptbase.c drivers/message/fusion/mptbase.h drivers/message/fusion/mptsas.c +3 more+1279 -4257 replies
3/6mpt fusion: Deleted functions for Firmware Event implementation using seperate WorkQueuedrivers/message/fusion/mptsas.c+0 -240 replies
4/6mpt fusion: SAS topology scan changes,Expander events, link status events addeddrivers/message/fusion/mptbase.h drivers/message/fusion/mptsas.c+572 -260 replies
4/6mpt fusion: Deleted functions for SAS topology scan changes,Expander events, link status events addeddrivers/message/fusion/mptsas.c+0 -2550 replies
6/6mpt fusion: Rescan SAS topology added.drivers/message/fusion/mptbase.h drivers/message/fusion/mptsas.c+194 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/6] mpt fusion: Firmware Event implementation using seperate WorkQueue

These patches are created on top of MPT fusion previous patch applied on date 26/02/2009 with subject line: "mpt fusion: config, Taskmgmt cmd, Internal cmd, Ioctl cmd changes"

Some patches are splited into two diffrent patches only for readability purpose for reviewer.

Consider below patches as one logical patch. There is no harm to send those patches as single patch, but to give more readability I have choosen to split.
PATCH 2 and PATCH 3.
PATCH 4 and PATCH 5.

PATCH 3 and PATCH 5 include only those function which are not part of MPT fusion.
---

---