public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Jiri Slaby <jirislaby@gmail.com>, Pavel Machek <pavel@suse.cz>,
	Christoph Hellwig <hch@lst.de>,
	Dominik Brodowski <linux@brodo.de>, Andi Kleen <ak@suse.de>,
	Adrian Bunk <bunk@stusta.de>, Greg Kroah-Hartman <gregkh@suse.de>,
	Nick Piggin <npiggin@suse.de>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Len Brown <len.brown@intel.com>
Subject: Re: Feature Removals for 2.6.25
Date: Thu, 31 Jan 2008 21:18:11 -0800	[thread overview]
Message-ID: <1201843092.23523.80.camel@brick> (raw)
In-Reply-To: <47A2A5D8.4080700@linux.intel.com>

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@linux.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@gmail.com>
Subject: [PATCH] feature-removal: document symbols going away

Signed-off-by: Harvey Harrison <harvey.harrison@gmail.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@linux.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@stusta.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@linux.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




  reply	other threads:[~2008-02-01  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:38 Feature Removals for 2.6.25 Harvey Harrison
2008-02-01  4:53 ` Arjan van de Ven
2008-02-01  5:18   ` Harvey Harrison [this message]
2008-02-01  6:33     ` Arjan van de Ven
2008-02-01  7:04       ` Harvey Harrison
2008-02-01  5:02 ` Feature Removals for 2.6.25 (USB driver api) Greg KH
2008-02-01  7:08 ` Feature Removals for 2.6.25 Stephen Hemminger
2008-02-02  1:29 ` Nick Piggin
2008-02-03 10:44 ` Feature Removals for 2.6.25 - old NCR53C9x driver Boaz Harrosh
2008-02-14  2:49 ` Feature Removals for 2.6.25 Bill Davidsen
2008-02-14  2:55   ` Stephen Hemminger
2008-02-14 18:16     ` Bill Davidsen
2008-02-14 18:24       ` Arjan van de Ven
2008-02-14 18:26         ` Christoph Hellwig
2008-02-14 23:20         ` David Newall
2008-02-15  3:27           ` Rene Herman

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=1201843092.23523.80.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=hch@lst.de \
    --cc=jirislaby@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=npiggin@suse.de \
    --cc=pavel@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=shemminger@linux-foundation.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