From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
Kumar Gala <galak@kernel.crashing.org>, Greg KH <greg@kroah.com>
Subject: [2.6 patch] the scheduled unexport of insert_resource
Date: Tue, 11 Apr 2006 00:14:55 +0200 [thread overview]
Message-ID: <20060410221455.GH2408@stusta.de> (raw)
This patch contains the scheduled unexport of insert_resource.
Kumar Gala said that some not yet submitted code uses it [1], but since
there is after one month still no code submission, and reverting the
exporting it again is trivial if it is both submitted and considered
acceptable for inclusion this shouldn't be a problem.
[1] http://lkml.org/lkml/2006/4/1/28
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Documentation/feature-removal-schedule.txt | 8 --------
include/linux/ioport.h | 2 +-
kernel/resource.c | 2 --
3 files changed, 1 insertion(+), 11 deletions(-)
--- linux-2.6.17-rc1-mm2-full/Documentation/feature-removal-schedule.txt.old 2006-04-10 20:52:23.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/Documentation/feature-removal-schedule.txt 2006-04-10 20:52:36.000000000 +0200
@@ -72,14 +72,6 @@
---------------------------
-What: remove EXPORT_SYMBOL(insert_resource)
-When: April 2006
-Files: kernel/resource.c
-Why: No modular usage in the kernel.
-Who: Adrian Bunk <bunk@stusta.de>
-
----------------------------
-
What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl])
When: November 2005
Files: drivers/pcmcia/: pcmcia_ioctl.c
--- linux-2.6.17-rc1-mm2-full/include/linux/ioport.h.old 2006-04-10 20:52:46.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/include/linux/ioport.h 2006-04-10 20:52:55.000000000 +0200
@@ -95,7 +95,7 @@
extern int request_resource(struct resource *root, struct resource *new);
extern struct resource * ____request_resource(struct resource *root, struct resource *new);
extern int release_resource(struct resource *new);
-extern __deprecated_for_modules int insert_resource(struct resource *parent, struct resource *new);
+extern int insert_resource(struct resource *parent, struct resource *new);
extern int allocate_resource(struct resource *root, struct resource *new,
u64 size,
u64 min, u64 max,
--- linux-2.6.17-rc1-mm2-full/kernel/resource.c.old 2006-04-10 20:53:04.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/kernel/resource.c 2006-04-10 20:53:11.000000000 +0200
@@ -381,8 +381,6 @@
return result;
}
-EXPORT_SYMBOL(insert_resource);
-
/*
* Given an existing resource, change its start and size to match the
* arguments. Returns -EBUSY if it can't fit. Existing children of
next reply other threads:[~2006-04-10 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 22:14 Adrian Bunk [this message]
2006-04-11 16:41 ` [2.6 patch] the scheduled unexport of insert_resource Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 22:07 Adrian Bunk
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=20060410221455.GH2408@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--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