From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: [PATCH -next] fs.h: fix functions for FILE_LOCKING disabled
Date: Tue, 28 Sep 2010 09:54:56 -0700 [thread overview]
Message-ID: <20100928095456.4b390540.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100928141823.8c61000e.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle•com>
Fix function signature warning when CONFIG_FILE_LOCKING is disabled.
include/linux/fs.h:1275: warning: function declaration isn't a prototype
include/linux/fs.h:1279: warning: function declaration isn't a prototype
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
---
include/linux/fs.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20100927.orig/include/linux/fs.h
+++ linux-next-20100927/include/linux/fs.h
@@ -1271,11 +1271,11 @@ static inline int lock_may_write(struct
return 1;
}
-static inline void lock_flocks()
+static inline void lock_flocks(void)
{
}
-static inline void unlock_flocks()
+static inline void unlock_flocks(void)
{
}
next prev parent reply other threads:[~2010-09-28 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 4:18 linux-next: Tree for September 28 Stephen Rothwell
2010-09-28 16:48 ` [PATCH -next] hwmon/pkgtemp: fix build error Randy Dunlap
2010-09-28 16:53 ` [PATCH -next] ceph: fix debugfs warnings Randy Dunlap
2010-09-28 19:42 ` Sage Weil
2010-09-28 16:54 ` Randy Dunlap [this message]
2010-09-28 16:56 ` [PATCH -next] pch_gbe: add header files Randy Dunlap
2010-09-28 17:34 ` David Miller
2010-09-28 16:58 ` [PATCH -next] sound/soc: fix printk format warning Randy Dunlap
2010-09-28 17:33 ` Mark Brown
2010-09-28 17:41 ` 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=20100928095456.4b390540.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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