From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: linux-next: build warning in Linus'tree Date: Wed, 26 May 2010 08:29:02 -0700 (PDT) Message-ID: References: <20100526110506.f2f4f22c.sfr@canb.auug.org.au> <20100525182040.f1882d0a.akpm@linux-foundation.org> <20100526140900.5b091c16.sfr@canb.auug.org.au> <20100525234116.71889c71.akpm@linux-foundation.org> <20100526171424.447fac18.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:44989 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752795Ab0EZPcp (ORCPT ); Wed, 26 May 2010 11:32:45 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Joakim Tjernlund Cc: Stephen Rothwell , Andrew Morton , linux-kernel@vger.kernel.org, linux-next@vger.kernel.org On Wed, 26 May 2010, Joakim Tjernlund wrote: > > If my suggestion above works, then one could start transforming current uses of __BYTE_ORDER, > into similar constructs and once all are done, #define both __LITTLE_ENDIAN/__BIG_ENDIAN and > move back to #if __BYTE_ORDER == __LITTLE_ENDIAN No. Don't do it. Why the hell would we want to use the inferior model? Linus