James,
The mpt3sas should be changed to mptsas. Just responding back to have
record on this problem is with old mptsas and not with mpt3sas managed
controllers.
Thanks
Sathya
-Original Message-
From: linux-scsi-ow...@vger.kernel.org
[mailto:linux-scsi-ow...@vger.kernel.org] On Behalf Of
Acked-by: Sathya Prakash Veerichetty
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: Monday, November 6, 2017 6:35 AM
To: Sathya Prakash; Chaitra P B; Suganath Prabu Subramani; James E.J.
Bottomley; Martin K. Petersen
Cc: Arnd Bergmann; Tomas Henzl; Sreekanth Reddy
Willy,
I think this patch had a problem and later modified to a different
blocking mechanism. Could you please pull in the latest change for this?
Thanks
Sathya
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Sunday, February 05, 2017 12:19 PM
To: linux-kernel@vger.kern
By removing the code below, we put all the commands for all the types of
devices (SAS/SATA) as simple-Q (requeue as the device require) and I am
not sure whether it is the intention of this change.
-Original Message-
From: Adam Manzanares [mailto:adam.manzana...@hgst.com]
Sent: Thursday, O
Our understanding is the relationship between the SCSI host and SAS end
devices is a parent-child and before ripping of SCSI host we need to rip of
all the children. Why the enclosure ends up trying to re-parent the SCSI
device from the enclosure to the SAS PHY even after we remove the SAS Phy?.
Do
Please consider this patch as Ack-by: Sathya Prakash
Veerichetty
PS: We don't have test environment to test this patch as this is for an
old controller. So ACKing based on code review and similar mpt3sas driver
code.
-Original Message-
From: Martin K. Petersen [mailto:martin.
Hi,
Please consider this patch as Ack-by: Sathya Prakash
Thanks,
Sathya
-Original Message-
From: mpt-fusionlinux@broadcom.com
[mailto:mpt-fusionlinux@broadcom.com] On Behalf Of Martin K. Petersen
Sent: Thursday, April 14, 2016 8:48 PM
To: Tina Ruchandani
Cc: mpt-fusionlinux@b
We need to do some more changes in this. The concept is first pool alloc
and then memory alloc in the pool, so the memory has to be freed if the
memory is allocated in the pool and irrespective of memory allocated or
not the pool has to be destroyed if it is created. We will work
internally and p
8 matches
Mail list logo