wake_up_inode() can become static.

Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>

---

 fs/inode.c                |   18 +++++++++---------
 include/linux/writeback.h |    1 -
 2 files changed, 9 insertions(+), 10 deletions(-)

--- linux-2.6.22-rc4-mm2/include/linux/writeback.h.old  2007-06-14 
02:00:29.000000000 +0200
+++ linux-2.6.22-rc4-mm2/include/linux/writeback.h      2007-06-14 
02:00:34.000000000 +0200
@@ -69,7 +69,6 @@
  * fs/fs-writeback.c
  */    
 int writeback_inodes(struct writeback_control *wbc);
-void wake_up_inode(struct inode *inode);
 int inode_wait(void *);
 int sync_inodes_sb(struct super_block *, int wait);
 int sync_inodes(int wait);
--- linux-2.6.22-rc4-mm2/fs/inode.c.old 2007-06-14 02:00:40.000000000 +0200
+++ linux-2.6.22-rc4-mm2/fs/inode.c     2007-06-14 02:02:25.000000000 +0200
@@ -99,6 +99,15 @@
 
 static struct kmem_cache * inode_cachep __read_mostly;
 
+static void wake_up_inode(struct inode *inode)
+{
+       /*
+        * Prevent speculative execution through spin_unlock(&inode_lock);
+        */
+       smp_mb();
+       wake_up_bit(&inode->i_state, __I_LOCK);
+}
+
 static struct inode *alloc_inode(struct super_block *sb)
 {
        static const struct address_space_operations empty_aops;
@@ -1296,15 +1305,6 @@
        spin_lock(&inode_lock);
 }
 
-void wake_up_inode(struct inode *inode)
-{
-       /*
-        * Prevent speculative execution through spin_unlock(&inode_lock);
-        */
-       smp_mb();
-       wake_up_bit(&inode->i_state, __I_LOCK);
-}
-
 /*
  * We rarely want to lock two inodes that do not have a parent/child
  * relationship (such as directory, child inode) simultaneously. The

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to