From: Larry Finger <Larry.Finger@lwfinger.net>
To: miklos@szeredi.hu, Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] fuse: Fix build error
Date: Fri, 10 Jul 2009 20:06:42 -0500 [thread overview]
Message-ID: <4A57E5A2.8060907@lwfinger.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
When building v2.6.31-rc2-344-g69ca06c, the following build errors are
found due to missing includes:
CC [M] fs/fuse/dev.o
fs/fuse/dev.c: In function ‘request_end’:
fs/fuse/dev.c:289: error: ‘BLK_RW_SYNC’ undeclared (first use in this
function)
fs/fuse/dev.c:289: error: (Each undeclared identifier is reported only
once
fs/fuse/dev.c:289: error: for each function it appears in.)
fs/fuse/dev.c:290: error: ‘BLK_RW_ASYNC’ undeclared (first use in this
function)
fs/fuse/dev.c: In function ‘fuse_request_send_nowait_locked’:
fs/fuse/dev.c:417: error: ‘BLK_RW_SYNC’ undeclared (first use in this
function)
fs/fuse/dev.c:418: error: ‘BLK_RW_ASYNC’ undeclared (first use in this
function)
make[2]: *** [fs/fuse/dev.o] Error 1
fs/nfs/write.c: In function ‘nfs_set_page_writeback’:
fs/nfs/write.c:207: error: ‘BLK_RW_ASYNC’ undeclared (first use in
this function)
fs/nfs/write.c:207: error: (Each undeclared identifier is reported
only once
fs/nfs/write.c:207: error: for each function it appears in.)
fs/nfs/write.c: In function ‘nfs_end_page_writeback’:
fs/nfs/write.c:220: error: ‘BLK_RW_ASYNC’ undeclared (first use in
this function)
CC lib/dump_stack.o
make[2]: *** [fs/nfs/write.o] Error 1
Signed-off-by: Larry Finger@lwfinger.net>
---
fuse/dev.c | 1 +
nfs/write.c | 1 +
2 files changed, 2 insertions(+)
Index: linux-2.6/fs/fuse/dev.c
===================================================================
--- linux-2.6.orig/fs/fuse/dev.c
+++ linux-2.6/fs/fuse/dev.c
@@ -16,6 +16,7 @@
#include <linux/pagemap.h>
#include <linux/file.h>
#include <linux/slab.h>
+#include <linux/blkdev.h>
MODULE_ALIAS_MISCDEV(FUSE_MINOR);
Index: linux-2.6/fs/nfs/write.c
===================================================================
--- linux-2.6.orig/fs/nfs/write.c
+++ linux-2.6/fs/nfs/write.c
@@ -19,6 +19,7 @@
#include <linux/nfs_mount.h>
#include <linux/nfs_page.h>
#include <linux/backing-dev.h>
+#include <linux/blkdev.h>
#include <asm/uaccess.h>
[-- Attachment #2: fix_fuse_build --]
[-- Type: text/plain, Size: 651 bytes --]
Index: linux-2.6/fs/fuse/dev.c
===================================================================
--- linux-2.6.orig/fs/fuse/dev.c
+++ linux-2.6/fs/fuse/dev.c
@@ -16,6 +16,7 @@
#include <linux/pagemap.h>
#include <linux/file.h>
#include <linux/slab.h>
+#include <linux/blkdev.h>
MODULE_ALIAS_MISCDEV(FUSE_MINOR);
Index: linux-2.6/fs/nfs/write.c
===================================================================
--- linux-2.6.orig/fs/nfs/write.c
+++ linux-2.6/fs/nfs/write.c
@@ -19,6 +19,7 @@
#include <linux/nfs_mount.h>
#include <linux/nfs_page.h>
#include <linux/backing-dev.h>
+#include <linux/blkdev.h>
#include <asm/uaccess.h>
reply other threads:[~2009-07-11 1:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A57E5A2.8060907@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®