On 11/28/2012 09:39 AM, Tejun Heo wrote:
Hey, Rafael.
On Wed, Nov 28, 2012 at 01:51:00AM +0100, Rafael J. Wysocki wrote:
Having considered that a bit more I'm now thinking that in fact the power
state
the device is in at the moment doesn't really matter, so the polling code
need
not
On Thu, 2012-11-15 at 15:51 -0500, Sasha Levin wrote:
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index ce5224c..77ba946 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -249,9 +249,9 @@ static DEVICE_ATTR(active_mode, S_IRUGO | S_IWUSR,
On Fri, 2012-11-16 at 19:56 +0800, NickCheng wrote:
From: Nick Cheng nick.ch...@areca.com.tw
Modify ARC-1214 IO behavior to make up for HW seldom malfunction.
Signed-off-by: Nick Cheng nick.ch...@areca.com.tw
This still isn't right. I said you could ignore most of the warnings
(like lines
On Friday, November 30, 2012 04:55:56 PM Aaron Lu wrote:
On 11/28/2012 09:39 AM, Tejun Heo wrote:
Hey, Rafael.
On Wed, Nov 28, 2012 at 01:51:00AM +0100, Rafael J. Wysocki wrote:
Having considered that a bit more I'm now thinking that in fact the power
state
the device is in at the
On 11/29/2012 05:02 PM, James Smart wrote:
Always possible - but Our f/w works at the FCP level and
below, which means it doesn't know/do SCSI commands - e.g what the
cdb within the FCP CMD frame is; know anything about SCSI device
classes and state; etc. And it shouldn't be required to do
On Mon, 2012-11-26 at 09:55 -0600, wenxi...@linux.vnet.ibm.com wrote:
plain text document attachment (fix_mem_alloc_fail)
Add code to handle memory allocation failures at module load time.
Reported-by: Fengguang Wu fengguang...@intel.com
Signed-off-by: Brian King brk...@linux.vnet.ibm.com
6 matches
Mail list logo