From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [PATCH 2.6.13 5/14] sas-class: sas_discover.c Discover process (end devices) Date: Tue, 13 Sep 2005 14:36:11 -0600 Message-ID: <20050913203611.GH32395@parisc-linux.org> References: <1126308304.4799.45.camel@mulgrave> <20050910024454.20602.qmail@web51613.mail.yahoo.com> <20050911094656.GC5429@infradead.org> <43251D8C.7020409@torque.net> <1126537041.4825.28.camel@mulgrave> <20050912164548.GB11455@us.ibm.com> <1126545680.4825.40.camel@mulgrave> <20050912184629.GA13489@us.ibm.com> <1126639342.4809.53.camel@mulgrave> <4327354E.7090409@adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4327354E.7090409@adaptec.com> Sender: linux-kernel-owner@vger.kernel.org To: Luben Tuikov Cc: James Bottomley , Patrick Mansfield , Douglas Gilbert , Christoph Hellwig , Luben Tuikov , Linux Kernel Mailing List , SCSI Mailing List List-Id: linux-scsi@vger.kernel.org On Tue, Sep 13, 2005 at 04:23:42PM -0400, Luben Tuikov wrote: > A SCSI LUN is not "u64 lun", it has never been and it will > never be. > > A SCSI LUN is "u8 LUN[8]" -- it is this from the Application > Layer down to the _transport layer_ (if you cared to look at > _any_ LL transport). Could you explain the difference please? Why is it preferable to keep the LUN as an array of bytes instead of a single large integer? > (It is also capitalized since it is an abbreviation.) Well, we have two conflicting standards to follow here. That of English which insists that abbreviations be capitalised, and that of the kernel which requires that all-caps identifiers be macros rather than structure members. We have to violate one.