From: Christoph Hellwig <hch@infradead.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: next-20081203 build failure, when building xfs_file.o
Date: Wed, 3 Dec 2008 07:55:34 -0500 [thread overview]
Message-ID: <20081203125534.GA8007@infradead.org> (raw)
In-Reply-To: <20081203124104.GA5400@linux.vnet.ibm.com>
On Wed, Dec 03, 2008 at 06:11:04PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
>
> next-20081203 kernel build fails on x86 with build failure
>
> In file included from fs/xfs/linux-2.6/xfs_file.c:39:
This is the fix I submitted for it yesterday:
--
fix compile on 32 bit systems
The recent compat patches make xfs_file.c include xfs_ioctl32.h unconditional,
which breaks the build on 32 bit systems which don't have the various compat
defintions.
Remove the include and move the defintion of xfs_file_compat_ioctl to
xfs_ioctl.h so that we can avoid including all the compat defintions in
xfs_file.c
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfs-master/fs/xfs/linux-2.6/xfs_file.c
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_file.c 2008-12-02 11:43:38.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_file.c 2008-12-02 11:44:06.000000000 +0100
@@ -36,9 +36,9 @@
#include "xfs_inode.h"
#include "xfs_error.h"
#include "xfs_rw.h"
-#include "xfs_ioctl32.h"
#include "xfs_vnodeops.h"
#include "xfs_da_btree.h"
+#include "xfs_ioctl.h"
#include <linux/dcache.h>
#include <linux/smp_lock.h>
Index: xfs-master/fs/xfs/linux-2.6/xfs_ioctl.h
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-02 11:44:10.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-02 11:44:52.000000000 +0100
@@ -67,4 +67,16 @@ xfs_attrmulti_attr_remove(
char *name,
__uint32_t flags);
+extern long
+xfs_file_compat_ioctl(
+ struct file *file,
+ unsigned int cmd,
+ unsigned long arg);
+
+extern long
+xfs_file_compat_ioctl_invis(
+ struct file *file,
+ unsigned int cmd,
+ unsigned long arg);
+
#endif
Index: xfs-master/fs/xfs/linux-2.6/xfs_ioctl32.h
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_ioctl32.h 2008-12-02 11:44:10.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_ioctl32.h 2008-12-02 11:44:18.000000000 +0100
@@ -20,9 +20,6 @@
#include <linux/compat.h>
-extern long xfs_file_compat_ioctl(struct file *, unsigned, unsigned long);
-extern long xfs_file_compat_invis_ioctl(struct file *, unsigned, unsigned long);
-
/*
* on 32-bit arches, ioctl argument structures may have different sizes
* and/or alignment. We define compat structures which match the
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: next-20081203 build failure, when building xfs_file.o
Date: Wed, 3 Dec 2008 07:55:34 -0500 [thread overview]
Message-ID: <20081203125534.GA8007@infradead.org> (raw)
In-Reply-To: <20081203124104.GA5400@linux.vnet.ibm.com>
On Wed, Dec 03, 2008 at 06:11:04PM +0530, Kamalesh Babulal wrote:
> Hi Stephen,
>
> next-20081203 kernel build fails on x86 with build failure
>
> In file included from fs/xfs/linux-2.6/xfs_file.c:39:
This is the fix I submitted for it yesterday:
--
fix compile on 32 bit systems
The recent compat patches make xfs_file.c include xfs_ioctl32.h unconditional,
which breaks the build on 32 bit systems which don't have the various compat
defintions.
Remove the include and move the defintion of xfs_file_compat_ioctl to
xfs_ioctl.h so that we can avoid including all the compat defintions in
xfs_file.c
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfs-master/fs/xfs/linux-2.6/xfs_file.c
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_file.c 2008-12-02 11:43:38.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_file.c 2008-12-02 11:44:06.000000000 +0100
@@ -36,9 +36,9 @@
#include "xfs_inode.h"
#include "xfs_error.h"
#include "xfs_rw.h"
-#include "xfs_ioctl32.h"
#include "xfs_vnodeops.h"
#include "xfs_da_btree.h"
+#include "xfs_ioctl.h"
#include <linux/dcache.h>
#include <linux/smp_lock.h>
Index: xfs-master/fs/xfs/linux-2.6/xfs_ioctl.h
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-02 11:44:10.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_ioctl.h 2008-12-02 11:44:52.000000000 +0100
@@ -67,4 +67,16 @@ xfs_attrmulti_attr_remove(
char *name,
__uint32_t flags);
+extern long
+xfs_file_compat_ioctl(
+ struct file *file,
+ unsigned int cmd,
+ unsigned long arg);
+
+extern long
+xfs_file_compat_ioctl_invis(
+ struct file *file,
+ unsigned int cmd,
+ unsigned long arg);
+
#endif
Index: xfs-master/fs/xfs/linux-2.6/xfs_ioctl32.h
===================================================================
--- xfs-master.orig/fs/xfs/linux-2.6/xfs_ioctl32.h 2008-12-02 11:44:10.000000000 +0100
+++ xfs-master/fs/xfs/linux-2.6/xfs_ioctl32.h 2008-12-02 11:44:18.000000000 +0100
@@ -20,9 +20,6 @@
#include <linux/compat.h>
-extern long xfs_file_compat_ioctl(struct file *, unsigned, unsigned long);
-extern long xfs_file_compat_invis_ioctl(struct file *, unsigned, unsigned long);
-
/*
* on 32-bit arches, ioctl argument structures may have different sizes
* and/or alignment. We define compat structures which match the
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-03 12:55 UTC|newest]
Thread overview: 30+ 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:41 ` Kamalesh Babulal
2008-12-03 12:55 ` Christoph Hellwig [this message]
2008-12-03 12:55 ` Christoph Hellwig
2008-12-03 14:15 ` Kamalesh Babulal
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 10:10 ` Mauro Carvalho Chehab
2008-12-06 11:28 ` 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 9:02 ` Geert Uytterhoeven
2008-12-04 12:13 ` Christoph Hellwig
2008-12-04 12:13 ` Christoph Hellwig
2008-12-04 12:46 ` Stephen Rothwell
2008-12-04 12:46 ` Stephen Rothwell
2008-12-04 12:50 ` Christoph Hellwig
2008-12-04 12:50 ` Christoph Hellwig
2008-12-04 13:23 ` 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=20081203125534.GA8007@infradead.org \
--to=hch@infradead.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.