summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/libsas/sas_ata.c
diff options
context:
space:
mode:
authorJames Bottomley <James.Bottomley@HansenPartnership.com>2007-12-30 12:37:31 -0600
committerJames Bottomley <James.Bottomley@HansenPartnership.com>2008-01-11 18:29:15 -0600
commit32e8ae36b8f80372015b88b63c4358a376c9af0f (patch)
tree9a7211c761b0476216eaf24f0aebd7ced7945a37 /drivers/scsi/libsas/sas_ata.c
parent2d507a01dac338831266b44ccbb01c69e84606ed (diff)
downloadop-kernel-dev-32e8ae36b8f80372015b88b63c4358a376c9af0f.zip
op-kernel-dev-32e8ae36b8f80372015b88b63c4358a376c9af0f.tar.gz
[SCSI] libsas: don't use made up error codes
This is bad for two reasons: 1. If they're returned to outside applications, no-one knows what they mean. 2. Eventually they'll clash with the ever expanding standard error codes. The problem error code in question is ETASK. I've replaced this by ECOMM (communications error on send) a network error code that seems to most closely relay what ETASK meant. Acked-by: Darrick J. Wong <djwong@us.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Diffstat (limited to 'drivers/scsi/libsas/sas_ata.c')
-rw-r--r--drivers/scsi/libsas/sas_ata.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/scsi/libsas/sas_ata.c b/drivers/scsi/libsas/sas_ata.c
index 0829b55..adc47d4 100644
--- a/drivers/scsi/libsas/sas_ata.c
+++ b/drivers/scsi/libsas/sas_ata.c
@@ -500,7 +500,7 @@ static int sas_execute_task(struct sas_task *task, void *buffer, int size,
goto ex_err;
}
wait_for_completion(&task->completion);
- res = -ETASK;
+ res = -ECOMM;
if (task->task_state_flags & SAS_TASK_STATE_ABORTED) {
int res2;
SAS_DPRINTK("task aborted, flags:0x%x\n",
OpenPOWER on IntegriCloud