diff options
| author |   James Bottomley <James.Bottomley@HansenPartnership.com> | 2007-12-30 12:37:31 -0600 |
|---|---|---|
| committer | James Bottomley <James.Bottomley@HansenPartnership.com> | 2008-01-11 18:29:15 -0600 |
| commit | 32e8ae36b8f80372015b88b63c4358a376c9af0f (patch) | |
| tree | 9a7211c761b0476216eaf24f0aebd7ced7945a37 /drivers/scsi/libsas/sas_expander.c | |
| parent | [SCSI] libsas, bsg: pass errors through correctly (diff) | |
| download | linux-dev-32e8ae36b8f80372015b88b63c4358a376c9af0f.tar.xz linux-dev-32e8ae36b8f80372015b88b63c4358a376c9af0f.zip | |
[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_expander.c')
| -rw-r--r-- | drivers/scsi/libsas/sas_expander.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c index 8aeaad95242c..aefd865a5788 100644 --- a/drivers/scsi/libsas/sas_expander.c +++ b/drivers/scsi/libsas/sas_expander.c @@ -96,7 +96,7 @@ static int smp_execute_task(struct domain_device *dev, void *req, int req_size, } wait_for_completion(&task->completion); - res = -ETASK; + res = -ECOMM; if ((task->task_state_flags & SAS_TASK_STATE_ABORTED)) { SAS_DPRINTK("smp task timed out or aborted\n"); i->dft->lldd_abort_task(task); |