[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1201843092.23523.80.camel@brick>
Date: Thu, 31 Jan 2008 21:18:11 -0800
From: Harvey Harrison <harvey.harrison@...il.com>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Jiri Slaby <jirislaby@...il.com>, Pavel Machek <pavel@...e.cz>,
Christoph Hellwig <hch@....de>,
Dominik Brodowski <linux@...do.de>, Andi Kleen <ak@...e.de>,
Adrian Bunk <bunk@...sta.de>,
Greg Kroah-Hartman <gregkh@...e.de>,
Nick Piggin <npiggin@...e.de>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Randy Dunlap <randy.dunlap@...cle.com>,
Len Brown <len.brown@...el.com>
Subject: Re: Feature Removals for 2.6.25
On Thu, 2008-01-31 at 20:53 -0800, Arjan van de Ven wrote:
> >
> > ---------------------------
> >
> > What: CONFIG_FORCED_INLINING
> > When: June 2006
> > Why: Config option is there to see if gcc is good enough. (in january
> > 2006). If it is, the behavior should just be the default. If it's not,
> > the option should just go away entirely.
> > Who: Arjan van de Ven
> >
> > Patch submitted to Arjan, maybe 2.6.25?
>
> Ingo picked it up, but no rush for .25, .26 is fine for this as well
>
OK, it shouldn't be any change from what's there now, but no rush.
> >
> > What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
> > (temporary transition config option provided until then)
> > The transition config option will also be removed at the same time.
> > When: before 2.6.19
> > Why: Unused symbols are both increasing the size of the kernel binary
> > and are often a sign of "wrong API"
> > Who: Arjan van de Ven <arjan@...ux.intel.com>
>
> this is an ongoing work; symbols get marked unused and then garbage collected
> when they're due; for example akpm has several of that kind in his pile right now
How do they get marked? As this is an ongoing effort, should this be
moved to the top of the file, and the actual symbols+date be listed?
That would make it easy to figure out what's going away.
Something like the following (grep found me two example symbols)
Harvey
---
From: Harvey Harrison <harvey.harrison@...il.com>
Subject: [PATCH] feature-removal: document symbols going away
Signed-off-by: Harvey Harrison <harvey.harrison@...il.com>
---
Documentation/feature-removal-schedule.txt | 25 +++++++++++++++----------
1 files changed, 15 insertions(+), 10 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 3a46d1f..0c418e6 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -5,6 +5,21 @@ the work. When the feature is removed from the kernel, it should also
be removed from this file.
---------------------------
+What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
+ (temporary transition config option provided until then)
+ The transition config option will also be removed at the same time.
+Why: Unused symbols are both increasing the size of the kernel binary
+ and are often a sign of "wrong API"
+Who: Arjan van de Ven <arjan@...ux.intel.com>
+
+When: 2.6.25
+fs/open.c:sys_open
+fs/read_write.c:sys_read
+
+When: 2.6.26
+
+
+---------------------------
What: MXSER
When: December 2007
@@ -137,16 +152,6 @@ Who: Adrian Bunk <bunk@...sta.de>
---------------------------
-What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports
- (temporary transition config option provided until then)
- The transition config option will also be removed at the same time.
-When: before 2.6.19
-Why: Unused symbols are both increasing the size of the kernel binary
- and are often a sign of "wrong API"
-Who: Arjan van de Ven <arjan@...ux.intel.com>
-
----------------------------
-
What: USB driver API moves to EXPORT_SYMBOL_GPL
When: February 2008
Files: include/linux/usb.h, drivers/usb/core/driver.c
--
1.5.4.rc4.1142.gf5a97
--
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