From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel Date: Sat, 1 Oct 2005 10:46:09 -0700 Message-ID: <20051001174609.GA13084@kroah.com> References: <547AF3BD0F3F0B4CBDC379BAC7E4189F01A9FA11@otce2k03.adaptec.com> <1128105594.10079.109.camel@bluto.andrew> <433D9035.6000504@adaptec.com> <1128111290.10079.147.camel@bluto.andrew> <20050930202234.GA2571@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20050930202234.GA2571@parisc-linux.org> Sender: linux-kernel-owner@vger.kernel.org To: Matthew Wilcox Cc: Andrew Patterson , Luben Tuikov , "Salyzyn, Mark" , dougg@torque.net, Linus Torvalds , Luben Tuikov , SCSI Mailing List , Linux Kernel Mailing List List-Id: linux-scsi@vger.kernel.org On Fri, Sep 30, 2005 at 02:22:34PM -0600, Matthew Wilcox wrote: > There's precedent for binary data in sysfs -- pci config space is one. binary data in sysfs is for stuff that is just a "pass through" for the kernel. Copying the pci config space, in raw form from the device to userspace is one such example. Firmware blobs is another one. Binary data in sysfs is _not_ for exporting kernel structures or other data that the kernel "understands" and manipulates. Hope this helps, greg k-h