public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christoph Hellwig <hch@infradead•org>
Cc: Geert Uytterhoeven <geert@linux-m68k•org>,
	Eric Sandeen <sandeen@sandeen•net>,
	Christoph Hellwig <hch@lst•de>, Lachlan McIlroy <lachlan@sgi•com>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	xfs@oss•sgi.com
Subject: Re: XFS breakage on m68k (was: Re: linux-next: Tree for December 3)
Date: Thu, 4 Dec 2008 23:46:03 +1100	[thread overview]
Message-ID: <20081204234603.b5a28cd6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081204121330.GA18815@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Hi Christoph,

On Thu, 4 Dec 2008 07:13:30 -0500 Christoph Hellwig <hch@infradead•org> wrote:
>
> 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.

I tried that tree but got this error from a powerpc ppc64_defconfig build
(which is 64 bit):

fs/xfs/linux-2.6/xfs_file.c:365: error: 'xfs_file_compat_invis_ioctl' undeclared here (not in a function)

Eric mentioned that your patch "had a problem of its own", so I assumed
that was it and left it removed from today's linux-next.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-04 12:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  7:36 linux-next: Tree for December 3 Stephen Rothwell
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-03 19:49 ` m68k 8390 breakage (was: Re: linux-next: Tree for December 3) Geert Uytterhoeven
2008-12-03 19:56   ` Stephen Hemminger
2008-12-03 20:38     ` Geert Uytterhoeven
2008-12-04  6:18       ` m68k 8390 breakage David Miller
2008-12-03 21:16 ` linux-next: Tree for December 3 (media/video/cx88) Randy Dunlap
2008-12-06 10:10   ` Mauro Carvalho Chehab
2008-12-06 11:28   ` Mauro Carvalho Chehab
2008-12-04  1:30 ` [PATCH -next] rtc twl4030: rename ioctl function when RTC_INTF_DEV=n Randy Dunlap
2008-12-09 10:02   ` Alessandro Zummo
2008-12-04  1:33 ` linux-next: Tree for December 3 (MFD) Randy Dunlap
2008-12-07 20:22   ` Samuel Ortiz
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
2008-12-04 12:46     ` Stephen Rothwell [this message]
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=20081204234603.b5a28cd6.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=hch@infradead$(echo .)org \
    --cc=hch@lst$(echo .)de \
    --cc=lachlan@sgi$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sandeen@sandeen$(echo .)net \
    --cc=xfs@oss$(echo .)sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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