linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/2] fs: define __sync_blockdev() when !BLOCK
Date: Tue,  5 May 2009 13:30:18 +0400	[thread overview]
Message-ID: <1241515818-15860-2-git-send-email-a.beregalov@gmail.com> (raw)
In-Reply-To: <1241515818-15860-1-git-send-email-a.beregalov@gmail.com>

Fix this build error when CONFIG_BLOCK is not set:
fs/sync.c: In function '__sync_filesystem':
fs/sync.c:40: error: implicit declaration of function '__sync_blockdev'

Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---
 include/linux/fs.h |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/include/linux/fs.h b/include/linux/fs.h
index efc991a..4193cf0 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1947,6 +1947,10 @@ extern int fsync_no_super(struct block_device *);
 #else
 static inline void bd_forget(struct inode *inode) {}
 static inline int sync_blockdev(struct block_device *bdev) { return 0; }
+static inline int __sync_blockdev(struct block_device *bdev, int wait)
+{
+	return 0;
+}
 static inline void sync_blockdevs(void) { }
 static inline void invalidate_bdev(struct block_device *bdev) {}
 
-- 
1.6.2.3


  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 [PATCH 1/2] fs: sync_filesystem() not depend on BLOCK Alexander Beregalov
2009-05-05  9:30 ` Alexander Beregalov [this message]
2009-05-06 16:07 ` 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-2-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).