From: Adrian Bunk <bunk@stusta.de>
To: mark.fasheh@oracle.com, kurt.hackel@oracle.com
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [2.6 patch] make ocfs2_create_new_lock() static
Date: Mon, 20 Nov 2006 03:24:28 +0100 [thread overview]
Message-ID: <20061120022428.GS31879@stusta.de> (raw)
This patch makes the needlessly global ocfs2_create_new_lock() static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
fs/ocfs2/dlmglue.c | 8 ++++----
fs/ocfs2/dlmglue.h | 2 --
2 files changed, 4 insertions(+), 6 deletions(-)
--- linux-2.6.19-rc5-mm2/fs/ocfs2/dlmglue.h.old 2006-11-20 02:04:48.000000000 +0100
+++ linux-2.6.19-rc5-mm2/fs/ocfs2/dlmglue.h 2006-11-20 02:04:55.000000000 +0100
@@ -68,8 +68,6 @@
u64 parent, struct inode *inode);
void ocfs2_lock_res_free(struct ocfs2_lock_res *res);
int ocfs2_create_new_inode_locks(struct inode *inode);
-int ocfs2_create_new_lock(struct ocfs2_super *osb,
- struct ocfs2_lock_res *lockres, int ex, int local);
int ocfs2_drop_inode_locks(struct inode *inode);
int ocfs2_data_lock_full(struct inode *inode,
int write,
--- linux-2.6.19-rc5-mm2/fs/ocfs2/dlmglue.c.old 2006-11-20 02:05:01.000000000 +0100
+++ linux-2.6.19-rc5-mm2/fs/ocfs2/dlmglue.c 2006-11-20 02:05:10.000000000 +0100
@@ -1063,10 +1063,10 @@
mlog_exit_void();
}
-int ocfs2_create_new_lock(struct ocfs2_super *osb,
- struct ocfs2_lock_res *lockres,
- int ex,
- int local)
+static int ocfs2_create_new_lock(struct ocfs2_super *osb,
+ struct ocfs2_lock_res *lockres,
+ int ex,
+ int local)
{
int level = ex ? LKM_EXMODE : LKM_PRMODE;
unsigned long flags;
next reply other threads:[~2006-11-20 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 2:24 Adrian Bunk [this message]
2006-11-20 3:58 ` Mark Fasheh
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=20061120022428.GS31879@stusta.de \
--to=bunk@stusta.de \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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
Powered by JetHome