From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Eric Sandeen <sandeen@sandeen.net>,
LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, linux-next@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: XFS breakage on m68k (was: Re: linux-next: Tree for December 3)
Date: Thu, 4 Dec 2008 07:13:30 -0500 [thread overview]
Message-ID: <20081204121330.GA18815@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812040956370.10635@anakin>
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
next prev parent reply other threads:[~2008-12-04 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081203183602.c06f8c39.sfr@canb.auug.org.au>
2008-12-03 12:41 ` next-20081203 build failure, when building xfs_file.o Kamalesh Babulal
2008-12-03 12:55 ` Christoph Hellwig
2008-12-03 14:15 ` Kamalesh Babulal
2008-12-04 9:02 ` XFS breakage on m68k (was: Re: linux-next: Tree for December 3) Geert Uytterhoeven
2008-12-04 12:13 ` Christoph Hellwig [this message]
2008-12-04 12:46 ` Stephen Rothwell
2008-12-04 12:50 ` Christoph Hellwig
2008-12-04 13:23 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081204121330.GA18815@infradead.org \
--to=hch@infradead.org \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox