From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: hch@infradead.org
Subject: unexport lookup_hash
Date: Fri, 3 Feb 2006 16:22:59 -0500 [thread overview]
Message-ID: <20060203212259.GA11066@redhat.com> (raw)
I just stumbled across this whilst checking for planned feature removal,
and missed any discussion why this didn't happen, so I assume Christoph forgot.
Signed-off-by: Dave Jones <davej@redhat.com>
--- linux-2.6.15.noarch/fs/namei.c~ 2006-02-03 16:20:49.000000000 -0500
+++ linux-2.6.15.noarch/fs/namei.c 2006-02-03 16:21:07.000000000 -0500
@@ -2668,7 +2668,6 @@ EXPORT_SYMBOL(follow_up);
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);
--- linux-2.6.15.noarch/Documentation/feature-removal-schedule.txt~ 2006-02-03 16:21:11.000000000 -0500
+++ linux-2.6.15.noarch/Documentation/feature-removal-schedule.txt 2006-02-03 16:21:40.000000000 -0500
@@ -116,13 +116,6 @@ Who: Harald Welte <laforge@netfilter.org
---------------------------
-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
next reply other threads:[~2006-02-03 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 21:22 Dave Jones [this message]
2006-02-03 22:32 ` unexport lookup_hash Adrian Bunk
2006-02-04 10:56 ` Christoph Hellwig
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=20060203212259.GA11066@redhat.com \
--to=davej@redhat.com \
--cc=hch@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.