From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH -next] fs: fix compat_ioctl build for CONFIG_BLOCK=n
Date: Mon, 14 Dec 2009 09:10:05 -0800 [thread overview]
Message-ID: <20091214091005.b4df65d9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091214165927.c08c4784.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix build failure when CONFIG_BLOCK=n:
fs/compat_ioctl.c:1604: error: 'SG_SET_TRANSFORM' undeclared
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
fs/compat_ioctl.c | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20091214.orig/fs/compat_ioctl.c
+++ linux-next-20091214/fs/compat_ioctl.c
@@ -1600,8 +1600,10 @@ static long do_ioctl_trans(int fd, unsig
case KDSKBMETA:
case KDSKBLED:
case KDSETLED:
+#ifdef CONFIG_BLOCK
/* SG stuff */
case SG_SET_TRANSFORM:
+#endif
/* AUTOFS */
case AUTOFS_IOC_READY:
case AUTOFS_IOC_FAIL:
next prev parent reply other threads:[~2009-12-14 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 5:59 linux-next: Tree for December 14 Stephen Rothwell
2009-12-14 16:44 ` [PATCH] staging/vt66*: kconfig, depends on WLAN Randy Dunlap
2009-12-14 17:08 ` [PATCH -next] radio/si470x: #include <sched.h> Randy Dunlap
2009-12-14 17:10 ` Randy Dunlap [this message]
2009-12-14 20:16 ` [PATCH -next] fs: fix compat_ioctl build for CONFIG_BLOCK=n Arnd Bergmann
2009-12-15 19:29 ` Randy Dunlap
2009-12-14 19:06 ` linux-next: Tree for December 14 (nouveau & AGP) Randy Dunlap
2009-12-14 19:51 ` [PATCH -next] nouveau: fix ch7006 build Randy Dunlap
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=20091214091005.b4df65d9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).