From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 0/2] cramfs: Add mount option "swapendian" Date: Thu, 15 Nov 2007 20:51:05 +0000 Message-ID: <20071115205105.GB30727@infradead.org> References: <200711152129.25686.lists-receive@programmierforen.de> <200711152135.16932.lists-receive@programmierforen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andi Drebes , linux-fsdevel@vger.kernel.org, Christoph Hellwig , Andrew Morton To: Linus Torvalds Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:36860 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752915AbXKOUvJ (ORCPT ); Thu, 15 Nov 2007 15:51:09 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Nov 15, 2007 at 12:46:11PM -0800, Linus Torvalds wrote: > > > On Thu, 15 Nov 2007, Linus Torvalds wrote: > > > > It would be *much* better to just standardize on one endianness, and be > > done with it. That way there are no config options, no confusion, and the > > code is smaller, simpler, and faster. > > .. it's also statically checkable with tools like "sparse", so it avoids > bugs not only by being simpler, but by simply being fundamentally more > robust to start with. We can do proper typechecking with sparse even for dual-endian filesystems, see ufs and sysvfs for example. And yes, for a new filesystems I'd always chose one endianes and stick to it, but becase I certain someone forgot that when creating cramfs we're stuck now :)