From: Alexander Beregalov <a.beregalov@gmail.com>
To: akpm@linux-foundation.org, thomas.petazzoni@free-electrons.com,
linux-kernel@vger.kernel.org, swhiteho@redhat.com,
cluster-devel@redhat.com
Subject: [PATCH -mm] fs.h: fix build error with !CONFIG_FILE_LOCKING
Date: Sat, 9 Aug 2008 02:32:28 +0400 [thread overview]
Message-ID: <20080808223228.GC5093@orion> (raw)
I am not sure it is a right way to fix it, please review.
Commit 4a70917f881a38ae688c98be9396f0a38f559094
(configure-out-file-locking-features) changed behaviour.
From: Alexander Beregalov <a.beregalov@gmail.com>
fs.h: fix build error with !CONFIG_FILE_LOCKING
fs/gfs2/ops_file.c:585: error: implicit declaration of function 'generic_setlease'
fs/gfs2/ops_file.c:637: error: implicit declaration of function '__mandatory_lock'
Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---
include/linux/fs.h | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index e9a7a7d..42d9ff9 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1051,6 +1051,8 @@ extern struct seq_operations locks_seq_operations;
#define flock_lock_file_wait(a, b) (-ENOLCK)
#define __break_lease(a, b) (0)
#define lease_get_mtime(a, b)
+#define generic_setlease(a, b, c) (0)
+#define vfs_setlease(a, b, c) (0)
#define lock_may_read(a, b, c) (1)
#define lock_may_write(a, b, c) (1)
#endif /* !CONFIG_FILE_LOCKING */
@@ -1647,6 +1649,7 @@ static inline int break_lease(struct inode *inode, unsigned int mode)
#else /* !CONFIG_FILE_LOCKING */
#define locks_mandatory_locked(a) (0)
#define locks_mandatory_area(a, b, c, d, e) (0)
+#define __mandatory_lock(a) (0)
#define mandatory_lock(a) (0)
#define locks_verify_locked(a) (0)
#define locks_verify_truncate(a, b, c) (0)
next reply other threads:[~2008-08-08 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 22:32 Alexander Beregalov [this message]
2008-08-14 9:19 ` [PATCH -mm] fs.h: fix build error with !CONFIG_FILE_LOCKING Thomas Petazzoni
2008-08-14 10:51 ` Alexander Beregalov
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=20080808223228.GC5093@orion \
--to=a.beregalov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
--cc=thomas.petazzoni@free-electrons.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.