[PATCH 18/31] scsi/aic7xxx: use kmemdup rather than duplicating its implementation

The patch was generated using fixed coccinelle semantic patch scripts/coccinelle/api/memdup.cocci [1]. [1]: http://permalink.gmane.org/gmane.linux.kernel/2014320 Signed-off-by: Andrzej Hajda a.ha...@samsung.com --- drivers/scsi/aic7xxx/aic79xx_core.c | 4 ++--

[PATCH 17/31] scsi/aacraid: use kmemdup rather than duplicating its implementation

The patch was generated using fixed coccinelle semantic patch scripts/coccinelle/api/memdup.cocci [1]. [1]: http://permalink.gmane.org/gmane.linux.kernel/2014320 Signed-off-by: Andrzej Hajda a.ha...@samsung.com --- drivers/scsi/aacraid/commctrl.c | 7 +++ 1 file changed, 3 insertions(+), 4

[PATCH 14/31] message/fusion: use kmemdup rather than duplicating its implementation

The patch was generated using fixed coccinelle semantic patch scripts/coccinelle/api/memdup.cocci [1]. [1]: http://permalink.gmane.org/gmane.linux.kernel/2014320 Signed-off-by: Andrzej Hajda a.ha...@samsung.com --- drivers/message/fusion/mptbase.c | 3 +-- 1 file changed, 1 insertion(+), 2

Re: [PATCH] scsi/be2iscsi: Fix logical-not-parentheses compilation warning

Tomer Barletz barl...@gmail.com writes: This fixes the following warning seen with GCC v5.1: warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses]. Signed-off-by: Tomer Barletz barl...@gmail.com --- drivers/scsi/be2iscsi/be_main.c | 2 +- 1

[PATCH v3 4/9] xen: Use correctly the Xen memory terminologies

Based on include/xen/mm.h [1], Linux is mistakenly using MFN when GFN is meant, I suspect this is because the first support for Xen was for PV. This resulted in some misimplementation of helpers on ARM and confused developers about the expected behavior. For instance, with pfn_to_mfn, we expect

[PATCH 1/7] megaraid_sas : Jbod sequence number support

Implemented JBOD map which will provide quick access for JBOD path and also provide sequence number. This will help hardware to fail command to the FW in case of any sequence mismatch. Fast Path IO for JBOD will refer JBOD map (which has sequence number per JBOD devices) instead of Raid map.

[PATCH 4/7] megaraid_sas : Print critical fw event message

Print firmware event in readable format. This will help user to track any critical firmware event without any application support. sample syslogd output - megaraid_sas :02:00.0: 8619 (491648347s/0x0020/WARN) - Controller temperature threshold exceeded. This may indicate inadequate system

[PATCH 0/7] megaraid_sas : Updates for scsi for-next

MegaRaid driver changes. Please consider this patch set for next kernel release. Signed-off-by: Sumit Saxena sumit.sax...@avagotech.com Signed-off-by: Kashyap Desai kashyap.de...@avagotech.com --- [PATCH 00/07] megaraid_sas : Updates for scsi for-next [PATCH 01/07] megaraid_sas : Jbod sequence

[PATCH 5/7] megaraid_sas : Fix validHandles check in io path

Syncro firmware support round robin IO switch on dual path. For this driver use validHandles as a check for dual path. This check suppose to be 1 (not 2) Without this patch, earlier driver code does not use dual path functionality. Signed-off-by: Sumit Saxena sumit.sax...@avagotech.com

[PATCH 3/7] megaraid_sas : Chip reset if driver fail to bring ioc ready

Patch which fix the issue reported as below. http://marc.info/?l=linux-scsim=143694494104544w=2 This patch will try to do chip reset from driver load time. Driver load time, if firmware is not comming to ready state, driver try chip reset calling adp_reset() callback. For fusion adapter, that

[PATCH 6/7] megaraid_sas : Code refactor for use of requestorId

Some of the code changes was proposed by David Binderman Removed redudant check of requestorId. Redundant condition: instance.requestorId. Check for plasma firmware 1.11 or new restructured to support only for specific device id Signed-off-by: Sumit Saxena sumit.sax...@avagotech.com

[PATCH 7/7] megaraid_sas : Version upgrade

Signed-off-by: Sumit Saxena sumit.sax...@avagotech.com Signed-off-by: Kashyap Desai kashyap.de...@avagotech.com --- diff --git a/megaraid_sas.h b/megaraid_sas.h index ccda60d..b1c605f 100644 --- a/megaraid_sas.h +++ b/megaraid_sas.h @@ -35,8 +35,8 @@ /* * MegaRAID SAS Driver meta data */

[PATCH 2/7] megaraid_sas : Support for max_io_size 1MB

Driver will expose max sge = 256 (earlier it was 64), if firmware support extended IO size upto 1M. Signed-off-by: Sumit Saxena sumit.sax...@avagotech.com Signed-off-by: Kashyap Desai kashyap.de...@avagotech.com --- diff --git a/megaraid_sas.h b/megaraid_sas.h index 45500ba..5db31c6 100644 ---