On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
>
> Updated 12G linkrate to libsas.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
>
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes ReineckezSeries & Storage
h...@
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> In Nexus reset the device state set to DS_IN_RECOVERY before doing
> phy reset and internal cleanup. Once internal cleanup finishes,
> the device state will set to DS_OPERATIONAL.
>
> Signed-off-by: Viswas G
> Signed-off-by:
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> In pm8001_ccb_task_free(), the dma unmapping is done based on
> ccb->n_elem value. This should be initialized to zero in the
> task_abort(). Otherwise, pm8001_ccb_task_free() will try for
> dma_unmap_sg() which is invalid for t
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> Thermal page code has been changed to 7 for the 12G controllers.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
> ---
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes Reinecke
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> If the link error happens, we don't need to disconnect the phy,
> which will remove the drive. Instead acknowledging the controller
> and logging the error will be enough.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh T
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> PORT RECOVERY TIMEOUT is the maximum time between the controller's
> detection of the PHY down until the receipt of the ID_Frame (from the
> same remote SAS port). If the time expires before the ID_FRAME is
> received, the port
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> The request has to be retried incase if the length of the SSP
> Response IU is invalid.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
> ---
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes Rei
On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
> From: Viswas G
>
> Bump pm80xx driver version to 0.1.38.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
> ---
> drivers/scsi/pm8001/pm8001_sas.h |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a
2015-07-29 8:27 GMT+02:00 :
> From: Viswas G
>
> This patch set contains bug fixes for pm80xx driver.
> Please consider these patches for next kernel release.
>
> Viswas G (8):
> pm80xx: Updated link rate
> pm80xx: Corrected device state changes in I_T_Nexus_Reset
> pm80xx: Update For Therm
On 07/29/2015 11:20 AM, Viswas G wrote:
>
> On Wed, Jul 29, 2015 at 2:26 PM, Hannes Reinecke wrote:
>> On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
>>> From: Viswas G
>>>
>>> If the link error happens, we don't need to disconnect the phy,
>>> which will remove the drive. Instead acknowledgin
On Wed, Jul 29, 2015 at 2:26 PM, Hannes Reinecke wrote:
> On 07/29/2015 08:27 AM, viswa...@pmcs.com wrote:
>> From: Viswas G
>>
>> If the link error happens, we don't need to disconnect the phy,
>> which will remove the drive. Instead acknowledging the controller
>> and logging the error will be
Hi James,
This patch is not pulled in yet.
Regards,
Suresh
-Original Message-
From: Jack Wang [mailto:xjtu...@gmail.com]
Sent: Tuesday, February 24, 2015 2:07 PM
To: Suresh Thiagarajan
Cc: linux-scsi@vger.kernel.org; James Bottomley; Viswas G; pmc...@pmcs.com
Subject: Re: [PATCH] pm80xx
On Wed, Jul 29, 2015 at 2:40 PM, Jack Wang wrote:
> 2015-07-29 8:27 GMT+02:00 :
>> From: Viswas G
>>
>> This patch set contains bug fixes for pm80xx driver.
>> Please consider these patches for next kernel release.
>>
>> Viswas G (8):
>> pm80xx: Updated link rate
>> pm80xx: Corrected device
Company has policy to use company email address, so update
my email address to company address.
Signed-off-by: Jack Wang
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a226416..c82f964 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
On Tue, Jul 28, 2015 at 04:02:45PM +0100, Julien Grall wrote:
[...]
> diff --git a/drivers/net/xen-netback/netback.c
> b/drivers/net/xen-netback/netback.c
> index 7d50711..3b7b7c3 100644
> --- a/drivers/net/xen-netback/netback.c
> +++ b/drivers/net/xen-netback/netback.c
> @@ -314,7 +314,7 @@ stati
On 28/07/15 16:02, Julien Grall wrote:
> Hi all,
>
> This patch series aims to use the memory terminologies described in
> include/linux/mm.h [1] for Linux xen code.
I mistakenly wrote the wrong include here. It should be include/xen/mm.h
from the Xen tree:
http://xenbits.xen.org/gitweb/?p=xen.g
On 28/07/15 18:16, David Vrabel wrote:
> On 28/07/15 16:02, Julien Grall wrote:
>> 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 brough some misimplementation of helpers on ARM and make the
Hi Boris,
On 28/07/15 20:12, Boris Ostrovsky wrote:
> On 07/28/2015 11:02 AM, Julien Grall wrote:
>> 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 brough some misimplementation of helpers o
Hi Chris,
On 28/07/15 20:39, Chris (Christopher) Brand wrote:
>> 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 brough
>> some
> Typo : "brought"
> Perhaps "resulted in" would be better ?
Hi Wei,
On 29/07/15 11:13, Wei Liu wrote:
> On Tue, Jul 28, 2015 at 04:02:45PM +0100, Julien Grall wrote:
> [...]
>> diff --git a/drivers/net/xen-netback/netback.c
>> b/drivers/net/xen-netback/netback.c
>> index 7d50711..3b7b7c3 100644
>> --- a/drivers/net/xen-netback/netback.c
>> +++ b/drivers/n
On 29/07/15 12:35, Julien Grall wrote:
> Hi Wei,
>
> On 29/07/15 11:13, Wei Liu wrote:
>> On Tue, Jul 28, 2015 at 04:02:45PM +0100, Julien Grall wrote:
>> [...]
>>> diff --git a/drivers/net/xen-netback/netback.c
>>> b/drivers/net/xen-netback/netback.c
>>> index 7d50711..3b7b7c3 100644
>>> --- a/d
On Wed, Jul 29, 2015 at 12:35:54PM +0100, Julien Grall wrote:
> Hi Wei,
>
> On 29/07/15 11:13, Wei Liu wrote:
> > On Tue, Jul 28, 2015 at 04:02:45PM +0100, Julien Grall wrote:
> > [...]
> >> diff --git a/drivers/net/xen-netback/netback.c
> >> b/drivers/net/xen-netback/netback.c
> >> index 7d50711
On 07/29/2015 07:25 AM, Julien Grall wrote:
Hi Boris,
On 28/07/15 20:12, Boris Ostrovsky wrote:
On 07/28/2015 11:02 AM, Julien Grall wrote:
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 broug
On 29/07/15 15:14, Boris Ostrovsky wrote:
>> static inline unsigned long pfn_to_gfn(unsigned long pfn)
>> {
>> if (xen_feature(XENFEAT_autotranslated_physmap))
>> return pfn;
>> else
>> return pfn_to_mfn(pfn);
>> }
>
>
> But you'd still say 'op.arg1.mfn = pfn_to_gfn(pfn);'
On 07/29/2015 10:23 AM, Julien Grall wrote:
On 29/07/15 15:14, Boris Ostrovsky wrote:
static inline unsigned long pfn_to_gfn(unsigned long pfn)
{
if (xen_feature(XENFEAT_autotranslated_physmap))
return pfn;
else
return pfn_to_mfn(pfn);
}
But you'd still say 'op.arg1
On 29.7.2015 08:27, viswa...@pmcs.com wrote:
> From: Viswas G
>
>
> Updated 12G linkrate to libsas.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
>
Reviewed-by: Tomas Henzl
Tomas
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a m
On 29.7.2015 08:27, viswa...@pmcs.com wrote:
> From: Viswas G
>
> In Nexus reset the device state set to DS_IN_RECOVERY before doing
> phy reset and internal cleanup. Once internal cleanup finishes,
> the device state will set to DS_OPERATIONAL.
>
> Signed-off-by: Viswas G
> Signed-off-by: Sure
On 29.7.2015 08:27, viswa...@pmcs.com wrote:
> From: Viswas G
>
> Thermal page code has been changed to 7 for the 12G controllers.
>
> Signed-off-by: Viswas G
> Signed-off-by: Suresh Thiagarajan
Reviewed-by: Tomas Henzl
Tomas
--
To unsubscribe from this list: send the line "unsubscribe lin
On 29.7.2015 08:27, viswa...@pmcs.com wrote:
> From: Viswas G
>
> In pm8001_ccb_task_free(), the dma unmapping is done based on
> ccb->n_elem value. This should be initialized to zero in the
> task_abort(). Otherwise, pm8001_ccb_task_free() will try for
> dma_unmap_sg() which is invalid for task
From: Colin Ian King
Trivial typo fix, \b should be \n
Signed-off-by: Colin Ian King
---
drivers/scsi/a100u2w.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/a100u2w.c b/drivers/scsi/a100u2w.c
index cac6b37..8086bd0 100644
--- a/drivers/scsi/a100u2w.c
+++ b/d
Trivial typo fixes:
o \b should be \n
o coalesce format to avoid excess spaces
Signed-off-by: Joe Perches
---
And another here:
drivers/scsi/pmcraid.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
index ed31d8c..b421de2
On 64 bit CPUs there is a memory corruption bug on probe(). It should
be a u32 pointer instead of an unsigned long pointer or we write past
the end of the setupdata[] array.
Signed-off-by: Dan Carpenter
---
Someone reported in 2003 that probe has a NULL deref so maybe it's
related to this memory
Subject: [PATCH v2 1/3] cxlflash: Base error recovery support
Date: Thu, 16 Jul 2015 18:26:35 -0500
From: Matthew R. Ochs
To: linux-scsi@vger.kernel.org,
james.bottom...@hansenpartnership.com, n...@linux-iscsi.org,
brk...@linux.vnet.ibm.com
CC: h...@infradead.org, mi...@neuling.org, imun...
Forwarded Message
Subject: [PATCH v2 3/3] cxlflash: Virtual LUN support
Date: Thu, 16 Jul 2015 18:26:57 -0500
From: Matthew R. Ochs
To: linux-scsi@vger.kernel.org,
james.bottom...@hansenpartnership.com, n...@linux-iscsi.org,
brk...@linux.vnet.ibm.com
CC: h...@infradead.or
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Jeff Moyer
> Sent: Wednesday, July 29, 2015 11:53 AM
> To: Christoph Hellwig
> Cc: Jens Axboe ; linux-ker...@vger.kernel.org;
> dmilb...@redhat.com
Adding linux-scs
On Wed, Jul 29, 2015 at 9:40 PM, Tomas Henzl wrote:
> On 29.7.2015 08:27, viswa...@pmcs.com wrote:
>> From: Viswas G
>>
>> In Nexus reset the device state set to DS_IN_RECOVERY before doing
>> phy reset and internal cleanup. Once internal cleanup finishes,
>> the device state will set to DS_OPE
From: Nicholas Bellinger
This patch addresses a v4.2-rc1 regression where backend driver
struct module unload immediately after ->free_device() has done
an internal call_rcu(), results in IRQ rcu_process_callbacks()
use-after-free paging OOPsen.
It adds a explicit synchronize_rcu() in target_bac
On 07/29/2015 08:39 PM, Joe Perches wrote:
> Trivial typo fixes:
>
> o \b should be \n
> o coalesce format to avoid excess spaces
>
> Signed-off-by: Joe Perches
> ---
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes ReineckezSeries & Storage
h...@suse.de
On 07/29/2015 11:36 PM, Dan Carpenter wrote:
> On 64 bit CPUs there is a memory corruption bug on probe(). It should
> be a u32 pointer instead of an unsigned long pointer or we write past
> the end of the setupdata[] array.
>
> Signed-off-by: Dan Carpenter
> ---
> Someone reported in 2003 that
On 07/29/2015 08:19 PM, Colin King wrote:
> From: Colin Ian King
>
> Trivial typo fix, \b should be \n
>
> Signed-off-by: Colin Ian King
> ---
Reviewed-by: Hannes Reinecke
Cheers,
Hannes
--
Dr. Hannes ReineckezSeries & Storage
h...@suse.de
40 matches
Mail list logo
