From: kbuild test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: kbuild-all@01.org, Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
devel@driverdev.osuosl.org, Yan Zheng <zyan@redhat.com>,
cluster-devel@redhat.com, Sage Weil <sage@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
fuse-devel@lists.sourceforge.net,
Christine Caulfield <ccaulfie@redhat.com>,
v9fs-developer@lists.sourceforge.net,
Ilya Dryomov <idryomov@gmail.com>,
linux-cifs@vger.kernel.org,
Eric Van Hensbergen <ericvh@gmail.com>,
Mark Fasheh <mfasheh@suse.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
David Teigland <teigland@redhat.com>,
Joel Becker <jlbec@evilplan.org>,
ceph-devel@vger.kernel.org, Abdu
Subject: [RFC PATCH] locks: posix_lock_inode_wait() can be static
Date: Fri, 23 Oct 2015 00:36:55 +0800 [thread overview]
Message-ID: <20151022163655.GA111096@roam> (raw)
In-Reply-To: <ded792d8fdcba562a1c74fd14fefcb387debc4b1.1445524157.git.bcodding@redhat.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
locks.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index daf4664..0d2b326 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1173,7 +1173,7 @@ EXPORT_SYMBOL(posix_lock_file);
*
* Apply a POSIX style lock request to an inode.
*/
-int posix_lock_inode_wait(struct inode *inode, struct file_lock *fl)
+static int posix_lock_inode_wait(struct inode *inode, struct file_lock *fl)
{
int error;
might_sleep ();
@@ -1860,7 +1860,7 @@ int fcntl_setlease(unsigned int fd, struct file *filp, long arg)
*
* Apply a FLOCK style lock request to an inode.
*/
-int flock_lock_inode_wait(struct inode *inode, struct file_lock *fl)
+static int flock_lock_inode_wait(struct inode *inode, struct file_lock *fl)
{
int error;
might_sleep();
prev parent reply other threads:[~2015-10-22 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 15:35 [PATCH 0/3] Minor cleanup for locks API Benjamin Coddington
2015-10-22 15:35 ` [PATCH 1/3] locks: introduce locks_lock_inode_wait() Benjamin Coddington
[not found] ` <daf0d3941f34438c1fbdc94a5f3a47c2b22f3ee8.1445524157.git.bcodding-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-22 15:59 ` kbuild test robot
2015-10-22 16:21 ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 2/3] Move locks API users to locks_lock_inode_wait() Benjamin Coddington
2015-10-22 15:35 ` [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait Benjamin Coddington
2015-10-22 16:36 ` kbuild test robot
2015-10-22 16:36 ` kbuild test robot [this message]
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=20151022163655.GA111096@roam \
--to=lkp@intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=ccaulfie@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=cluster-devel@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=ericvh@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=jlbec@evilplan.org \
--cc=kbuild-all@01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mfasheh@suse.com \
--cc=miklos@szeredi.hu \
--cc=oleg.drokin@intel.com \
--cc=sage@redhat.com \
--cc=teigland@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
--cc=zyan@redhat.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 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).