[<prev] [next>] [day] [month] [year] [list]
Message-ID: <490A78FE.20201@cn.fujitsu.com>
Date: Fri, 31 Oct 2008 11:18:22 +0800
From: Zhaolei <zhaolei@...fujitsu.com>
To: linux-kernel@...r.kernel.org
CC: viro@...iv.linux.org.uk, mtk.manpages@...il.com,
rdunlap@...otime.net, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: [PATCH] Correct wrong function name of d_put in kernel document and
source comment
no function named d_put(), it should be dput().
Impact: fix document and comment, no functionality changed
Signed-off-by: Zhao Lei <zhaolei@...fuijtsu.com>
---
Documentation/filesystems/vfs.txt | 2 +-
fs/dcache.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index c4d348d..e663178 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -960,7 +960,7 @@ manipulate dentries:
d_lookup: look up a dentry given its parent and path name component
It looks up the child of that given name from the dcache
hash table. If it is found, the reference count is incremented
- and the dentry is returned. The caller must use d_put()
+ and the dentry is returned. The caller must use dput()
to free the dentry when it finishes using it.
For further information on dentry locking, please refer to the document
diff --git a/fs/dcache.c b/fs/dcache.c
index a1d86c7..db2bc6a 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -1336,7 +1336,7 @@ err_out:
*
* Searches the children of the parent dentry for the name in question. If
* the dentry is found its reference count is incremented and the dentry
- * is returned. The caller must use d_put to free the entry when it has
+ * is returned. The caller must use dput to free the entry when it has
* finished using it. %NULL is returned on failure.
*
* __d_lookup is dcache_lock free. The hash list is protected using RCU.
--
1.5.5.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists