From: Adrian Bunk <bunk@stusta.de>
To: neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [2.6 patch] fs/lockd/clntproc.c: make 2 functions static
Date: Sat, 8 Jan 2005 22:53:29 +0100 [thread overview]
Message-ID: <20050108215329.GZ14108@stusta.de> (raw)
The patch below makes two needlessly global functions static.
diffstat output:
fs/lockd/clntproc.c | 4 ++--
include/linux/lockd/lockd.h | 2 --
2 files changed, 2 insertions(+), 4 deletions(-)
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.10-mm2-full/include/linux/lockd/lockd.h.old 2005-01-08 04:29:36.000000000 +0100
+++ linux-2.6.10-mm2-full/include/linux/lockd/lockd.h 2005-01-08 04:30:09.000000000 +0100
@@ -143,8 +143,6 @@
* Lockd client functions
*/
struct nlm_rqst * nlmclnt_alloc_call(void);
-int nlmclnt_call(struct nlm_rqst *, u32);
-int nlmclnt_async_call(struct nlm_rqst *, u32, rpc_action);
int nlmclnt_block(struct nlm_host *, struct file_lock *, u32 *);
int nlmclnt_cancel(struct nlm_host *, struct file_lock *);
u32 nlmclnt_grant(struct nlm_lock *);
--- linux-2.6.10-mm2-full/fs/lockd/clntproc.c.old 2005-01-08 04:29:49.000000000 +0100
+++ linux-2.6.10-mm2-full/fs/lockd/clntproc.c 2005-01-08 04:30:15.000000000 +0100
@@ -322,7 +322,7 @@
/*
* Generic NLM call
*/
-int
+static int
nlmclnt_call(struct nlm_rqst *req, u32 proc)
{
struct nlm_host *host = req->a_host;
@@ -428,7 +428,7 @@
return status;
}
-int
+static int
nlmclnt_async_call(struct nlm_rqst *req, u32 proc, rpc_action callback)
{
struct nlm_host *host = req->a_host;
next reply other threads:[~2005-01-08 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 21:53 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-24 20:26 [2.6 patch] fs/lockd/clntproc.c: make 2 functions static Adrian Bunk
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=20050108215329.GZ14108@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.