On Sun, Dec 30, 2007 at 12:37:31PM -0600, James Bottomley wrote: > 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. Yay, cleanups :) Acked-by: Darrick J. Wong <djwong@xxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
