[SCSI] libsas: don't use made up error codes
authorJames Bottomley <James.Bottomley@HansenPartnership.com>
Sun, 30 Dec 2007 18:37:31 +0000 (12:37 -0600)
committerJames Bottomley <James.Bottomley@HansenPartnership.com>
Sat, 12 Jan 2008 00:29:15 +0000 (18:29 -0600)
commit32e8ae36b8f80372015b88b63c4358a376c9af0f
tree9a7211c761b0476216eaf24f0aebd7ced7945a37
parent2d507a01dac338831266b44ccbb01c69e84606ed
[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>
drivers/scsi/libsas/sas_ata.c
drivers/scsi/libsas/sas_expander.c
include/scsi/libsas.h