Re: [PATCH] libsas: don't use made up error codes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2007-12-31 at 13:25 -0800, Darrick J. Wong wrote:
> 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 :)

Don't get your hopes up ... this was just one that unavoidably crossed
my attention path while I was doing something else.  I'm not going out
looking for these things ... mainly for fear of finding them in large
quantities.

James


-
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux