From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] unexport kmap_{pte,port}
Date: Fri, 21 Jan 2005 11:09:23 +0100 [thread overview]
Message-ID: <20050121100923.GH3209@stusta.de> (raw)
I haven't found any modular usage of kmap_{pte,port} on !ppc in the
kernel.
Is this patch correct?
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
arch/i386/mm/init.c | 3 ---
arch/mips/mm/init.c | 3 ---
arch/sparc/mm/init.c | 3 ---
3 files changed, 9 deletions(-)
--- linux-2.6.11-rc1-mm2-full/arch/i386/mm/init.c.old 2005-01-20 23:45:08.000000000 +0100
+++ linux-2.6.11-rc1-mm2-full/arch/i386/mm/init.c 2005-01-20 23:45:20.000000000 +0100
@@ -252,9 +252,6 @@
pte_t *kmap_pte;
pgprot_t kmap_prot;
-EXPORT_SYMBOL(kmap_prot);
-EXPORT_SYMBOL(kmap_pte);
-
#define kmap_get_fixmap_pte(vaddr) \
pte_offset_kernel(pmd_offset(pud_offset(pgd_offset_k(vaddr), vaddr), (vaddr)), (vaddr))
--- linux-2.6.11-rc1-mm2-full/arch/sparc/mm/init.c.old 2005-01-20 23:45:27.000000000 +0100
+++ linux-2.6.11-rc1-mm2-full/arch/sparc/mm/init.c 2005-01-20 23:45:32.000000000 +0100
@@ -59,9 +59,6 @@
pte_t *kmap_pte;
pgprot_t kmap_prot;
-EXPORT_SYMBOL(kmap_prot);
-EXPORT_SYMBOL(kmap_pte);
-
#define kmap_get_fixmap_pte(vaddr) \
pte_offset_kernel(pmd_offset(pgd_offset_k(vaddr), (vaddr)), (vaddr))
--- linux-2.6.11-rc1-mm2-full/arch/mips/mm/init.c.old 2005-01-20 23:45:39.000000000 +0100
+++ linux-2.6.11-rc1-mm2-full/arch/mips/mm/init.c 2005-01-20 23:45:46.000000000 +0100
@@ -83,9 +83,6 @@
pte_t *kmap_pte;
pgprot_t kmap_prot;
-EXPORT_SYMBOL(kmap_prot);
-EXPORT_SYMBOL(kmap_pte);
-
#define kmap_get_fixmap_pte(vaddr) \
pte_offset_kernel(pmd_offset(pgd_offset_k(vaddr), (vaddr)), (vaddr))
reply other threads:[~2005-01-21 10:14 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=20050121100923.GH3209@stusta.de \
--to=bunk@stusta.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 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.