Re: [PATCH v1.0 2/16] arcmsr: Support MSI-X interrupt

2014-05-02 Thread Dan Carpenter
On Wed, Apr 30, 2014 at 05:50:12PM +0800, ching wrote: From: Chingching2...@areca.com.tw Adding code for supporting MSI-X interrupt Signed-off-by: Chingching2...@areca.com.tw --- These patches seem to be broken up nicely into patches which do one thing per patch and they are much easier

Re: [PATCH v1.0 12/16] arcmsr: revise alloction of second dma_coherent_handle for type B adapter

2014-05-02 Thread Dan Carpenter
On Wed, Apr 30, 2014 at 07:30:29PM +0800, ching wrote: From: Chingching2...@areca.com.tw Revise allocation of second dma_coherent_handle for type_B adapter. Is this a bugfix? I think it is. Do you know what the user visible effects are? regards, dan carpenter -- To unsubscribe from this

Re: [PATCH v1.0 16/16] arcmsr: support new adapter ARC12x4

2014-05-02 Thread Dan Carpenter
On Wed, Apr 30, 2014 at 07:46:18PM +0800, ching wrote: + acb-pmuD = reg; + reg-chip_id = (u32 __iomem *)((unsigned long)acb-mem_base0 + + ARCMSR_ARC1214_CHIP_ID); + reg-cpu_mem_config = (u32 __iomem *)((unsigned long) + acb-mem_base0 +

Re: [PATCH v1.0 1/11] arcmsr: Revise interrupt service routine relate function

2014-05-02 Thread 黃清隆
Hi James, Indeed, it makes you confusion that I mistake typing the subject. It should be [PATCH v1.0 1/16] , but not [PATCH v1.0 1/11]. Why I use v1.0 other than v1.4? Changing from 11 patches to 16 patches. Because I spend a long time to simplify each patch, so patch number is increase. It is

Re: [PATCH v1.0 2/16] arcmsr: Support MSI-X interrupt

2014-05-02 Thread ching
Thanks for Dan's advice. I will revise the patch code. Next upload will be PATCH v1.1 16 patches. On Fri, 2014-05-02 at 11:31 +0300, Dan Carpenter wrote: On Wed, Apr 30, 2014 at 05:50:12PM +0800, ching wrote: From: Chingching2...@areca.com.tw Adding code for supporting MSI-X interrupt

RE: [patch] [SCSI] mpt3sas: tidy up output slightly

2014-05-02 Thread Reddy, Sreekanth
James, This patch seem to be fine. Please consider this patch. Regards, Sreekanth -Original Message- From: Dan Carpenter [mailto:dan.carpen...@oracle.com] Sent: Friday, March 28, 2014 2:09 PM To: Nandigama, Nagalakshmi Cc: Reddy, Sreekanth; Support; James E.J. Bottomley; DL-MPT Fusion

Re: [PATCH 0/3] libsas: add support for port multiplier

2014-05-02 Thread Tejun Heo
On Thu, Apr 24, 2014 at 09:27:03PM +0800, Xiangliang Yu wrote: This patch set will support SATA port multiplier(PM) in LIBSAS. LIBSAS is need to implement several key handling to support SATA PM: First,low level driver notify libsas that SATA PM is attached to HBA port. Then, LIBSAS will

Re: [PATCH 0/3] libsas: add support for port multiplier

2014-05-02 Thread Dan Williams
On Fri, May 2, 2014 at 8:36 AM, Tejun Heo t...@kernel.org wrote: On Thu, Apr 24, 2014 at 09:27:03PM +0800, Xiangliang Yu wrote: This patch set will support SATA port multiplier(PM) in LIBSAS. LIBSAS is need to implement several key handling to support SATA PM: First,low level driver notify

Re: [PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-05-02 Thread Joe Lawrence
On Wed, 2 Apr 2014 16:48:52 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:40:41 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: Since bsg creation is a side effect of sas_rphy_add, move its complementary removal call into sas_rphy_remove. Hello James,

Re: [PATCH RESEND] scsi_transport_sas: move bsg destructor into sas_rphy_remove

2014-05-02 Thread Dan Williams
On Fri, May 2, 2014 at 12:01 PM, Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:48:52 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: On Wed, 2 Apr 2014 16:40:41 -0400 Joe Lawrence joe.lawre...@stratus.com wrote: Since bsg creation is a side effect of sas_rphy_add,

[PATCH 4/4] [SCSI]fnic: assign FIP_ALL_FCF_MACS to fcoe_all_fcfs

2014-05-02 Thread Hiral Shah
1) Assgning FIP_ALL_FCF_MACS to fcoe_all_fcfs allows VLAN request to be sent to correct Mac address for VLAN Discovery otherwise VLAN request will be sent to invalid address hence FLOGI never happens. 2) Simplify the copy_and_format_trace_data code and log the correct Link event for fnic control