From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id mB4CDfnK024829 for ; Thu, 4 Dec 2008 06:13:41 -0600 Date: Thu, 4 Dec 2008 07:13:30 -0500 From: Christoph Hellwig Subject: Re: XFS breakage on m68k (was: Re: linux-next: Tree for December 3) Message-ID: <20081204121330.GA18815@infradead.org> References: <20081203183602.c06f8c39.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Geert Uytterhoeven Cc: Stephen Rothwell , Eric Sandeen , LKML , xfs@oss.sgi.com, linux-next@vger.kernel.org, Christoph Hellwig On Thu, Dec 04, 2008 at 10:02:15AM +0100, Geert Uytterhoeven wrote: > On Wed, 3 Dec 2008, Stephen Rothwell wrote: > > Status of my local build tests will be at > > http://kisskb.ellerman.id.au/linux-next . If maintainers want to give > > advice about cross compilers/configs that work, we are always open to add > > more builds. > > On m68k (32-bit only, no compat32), XFS fails to build in linux-next: Yeah, it's broken on all 32bit platforms. Today's xfs tree has a fix for it. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs