From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] fs/namei.c: make lookup_hash() static
Date: Fri, 3 Feb 2006 22:04:47 +0100 [thread overview]
Message-ID: <20060203210447.GM4408@stusta.de> (raw)
As announced, lookup_hash() can now become static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Documentation/feature-removal-schedule.txt | 7 -------
fs/namei.c | 3 +--
include/linux/namei.h | 1 -
3 files changed, 1 insertion(+), 10 deletions(-)
--- linux-2.6.16-rc1-mm5-full/Documentation/feature-removal-schedule.txt.old 2006-02-03 16:44:06.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/Documentation/feature-removal-schedule.txt 2006-02-03 16:44:16.000000000 +0100
@@ -116,13 +116,6 @@
---------------------------
-What: EXPORT_SYMBOL(lookup_hash)
-When: January 2006
-Why: Too low-level interface. Use lookup_one_len or lookup_create instead.
-Who: Christoph Hellwig <hch@lst.de>
-
----------------------------
-
What: CONFIG_FORCED_INLINING
When: June 2006
Why: Config option is there to see if gcc is good enough. (in january
--- linux-2.6.16-rc1-mm5-full/include/linux/namei.h.old 2006-02-03 16:44:22.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/include/linux/namei.h 2006-02-03 16:44:26.000000000 +0100
@@ -75,7 +75,6 @@
extern void release_open_intent(struct nameidata *);
extern struct dentry * lookup_one_len(const char *, struct dentry *, int);
-extern __deprecated_for_modules struct dentry * lookup_hash(struct nameidata *);
extern int follow_down(struct vfsmount **, struct dentry **);
extern int follow_up(struct vfsmount **, struct dentry **);
--- linux-2.6.16-rc1-mm5-full/fs/namei.c.old 2006-02-03 16:44:34.000000000 +0100
+++ linux-2.6.16-rc1-mm5-full/fs/namei.c 2006-02-03 16:44:46.000000000 +0100
@@ -1248,7 +1248,7 @@
return dentry;
}
-struct dentry * lookup_hash(struct nameidata *nd)
+static struct dentry * lookup_hash(struct nameidata *nd)
{
return __lookup_hash(&nd->last, nd->dentry, nd);
}
@@ -2661,7 +2661,6 @@
EXPORT_SYMBOL(get_write_access); /* binfmt_aout */
EXPORT_SYMBOL(getname);
EXPORT_SYMBOL(lock_rename);
-EXPORT_SYMBOL(lookup_hash);
EXPORT_SYMBOL(lookup_one_len);
EXPORT_SYMBOL(page_follow_link_light);
EXPORT_SYMBOL(page_put_link);
reply other threads:[~2006-02-03 21:04 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=20060203210447.GM4408@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--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