From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] fs/inode.c: make iprune_mutex static
Date: Mon, 20 Feb 2006 23:36:21 +0100 [thread overview]
Message-ID: <20060220223621.GN4661@stusta.de> (raw)
There's no reason for iprune_mutex being global.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
fs/inode.c | 2 +-
include/linux/fs.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
--- linux-2.6.16-rc4-mm1-full/include/linux/fs.h.old 2006-02-20 19:43:08.000000000 +0100
+++ linux-2.6.16-rc4-mm1-full/include/linux/fs.h 2006-02-20 19:43:14.000000000 +0100
@@ -1562,7 +1562,6 @@
extern struct inode *new_inode(struct super_block *);
extern int remove_suid(struct dentry *);
extern void remove_dquot_ref(struct super_block *, int, struct list_head *);
-extern struct mutex iprune_mutex;
extern void __insert_inode_hash(struct inode *, unsigned long hashval);
extern void remove_inode_hash(struct inode *);
--- linux-2.6.16-rc4-mm1-full/fs/inode.c.old 2006-02-20 19:43:23.000000000 +0100
+++ linux-2.6.16-rc4-mm1-full/fs/inode.c 2006-02-20 19:43:32.000000000 +0100
@@ -91,7 +91,7 @@
* from its final dispose_list, the struct super_block they refer to
* (for inode->i_sb->s_op) may already have been freed and reused.
*/
-DEFINE_MUTEX(iprune_mutex);
+static DEFINE_MUTEX(iprune_mutex);
/*
* Statistics gathering..
reply other threads:[~2006-02-20 22:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060220223621.GN4661@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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