James Bottomley 32e8ae36b8 [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>		2008-01-11 18:29:15 -06:00
..
Kconfig	[SCSI] libsas: add host SMP processing	2008-01-11 18:29:11 -06:00
Makefile	[SCSI] libsas: add host SMP processing	2008-01-11 18:29:11 -06:00
sas_ata.c	[SCSI] libsas: don't use made up error codes	2008-01-11 18:29:15 -06:00
sas_discover.c	[SCSI] libsas: Convert sas_proto users to sas_protocol	2008-01-11 18:22:41 -06:00
sas_dump.c
sas_dump.h
sas_event.c
sas_expander.c	[SCSI] libsas: don't use made up error codes	2008-01-11 18:29:15 -06:00
sas_host_smp.c	[SCSI] libsas: add host SMP processing	2008-01-11 18:29:11 -06:00
sas_init.c
sas_internal.h	[SCSI] libsas: add host SMP processing	2008-01-11 18:29:11 -06:00
sas_phy.c
sas_port.c
sas_scsi_host.c	[SCSI] libsas: Fix various sparse complaints	2008-01-11 18:22:41 -06:00