From: Alexander Beregalov <a.beregalov@gmail.com>
To: linux-next@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk
Cc: Alexander Beregalov <a.beregalov@gmail.com>
Subject: [PATCH 1/2] fs: sync_filesystem() not depend on BLOCK
Date: Tue, 5 May 2009 13:30:17 +0400 [thread overview]
Message-ID: <1241515818-15860-1-git-send-email-a.beregalov@gmail.com> (raw)
Fix this build error when CONFIG_BLOCK is not set:
fs/super.c: In function 'generic_shutdown_super':
fs/super.c:278: error: implicit declaration of function 'sync_filesystem'
sync_filesystem() is always built with or without BLOCK.
Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---
include/linux/fs.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index dee9745..efc991a 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1943,7 +1943,6 @@ extern struct super_block *freeze_bdev(struct block_device *);
extern void emergency_thaw_all(void);
extern int thaw_bdev(struct block_device *bdev, struct super_block *sb);
extern int fsync_bdev(struct block_device *);
-extern int sync_filesystem(struct super_block *);
extern int fsync_no_super(struct block_device *);
#else
static inline void bd_forget(struct inode *inode) {}
@@ -1961,6 +1960,8 @@ static inline int thaw_bdev(struct block_device *bdev, struct super_block *sb)
return 0;
}
#endif
+extern int sync_filesystem(struct super_block *);
+
extern const struct file_operations def_blk_fops;
extern const struct file_operations def_chr_fops;
extern const struct file_operations bad_sock_fops;
--
1.6.2.3
next reply other threads:[~2009-05-05 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 9:30 Alexander Beregalov [this message]
2009-05-05 9:30 ` [PATCH 2/2] fs: define __sync_blockdev() when !BLOCK Alexander Beregalov
2009-05-06 16:07 ` [PATCH 1/2] fs: sync_filesystem() not depend on BLOCK Al Viro
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=1241515818-15860-1-git-send-email-a.beregalov@gmail.com \
--to=a.beregalov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).