From: Christoph Hellwig <hch@lst.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 14:23:27 +0100 [thread overview]
Message-ID: <20081204132327.GA12971@lst.de> (raw)
In-Reply-To: <20081204125006.GA13411@infradead.org>
On Thu, Dec 04, 2008 at 07:50:06AM -0500, Christoph Hellwig wrote:
> Yeah, but Niv fixed it up and the correct version is not in the xfs git
> tree.
Hah, he noticed the bug but the wrong version got checked in anyway.
Here's the fix (for todays xfs tree):
--
[XFS] Fix compile with CONFIG_COMPAT enabled
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfs/fs/xfs/linux-2.6/xfs_ioctl.h
===================================================================
--- xfs.orig/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-04 14:19:32.000000000 +0100
+++ xfs/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-04 14:19:38.000000000 +0100
@@ -74,7 +74,7 @@ xfs_file_compat_ioctl(
unsigned long arg);
extern long
-xfs_file_compat_ioctl_invis(
+xfs_file_compat_invis_ioctl(
struct file *file,
unsigned int cmd,
unsigned long arg);
prev parent reply other threads:[~2008-12-04 13:33 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
2008-12-04 12:50 ` Christoph Hellwig
2008-12-04 13:23 ` Christoph Hellwig [this message]
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=20081204132327.GA12971@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=lachlan@sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).