linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	arjan@infradead.org, linux-kernel@vger.kernel.org,
	jtk@us.ibm.com, wtaber@us.ibm.com, pbadari@us.ibm.com,
	markv@us.ibm.com, greghk@us.ibm.com,
	Linus Torvalds <torvalds@osdl.org>,
	dipankar@in.ibm.com
Subject: Re: [PATCH] add feature-removal-schedule.txt documentation
Date: Sat, 8 Jan 2005 10:32:20 -0800	[thread overview]
Message-ID: <20050108183220.GA2033@us.ibm.com> (raw)
In-Reply-To: <20050106235633.GA10110@kroah.com>

On Thu, Jan 06, 2005 at 03:56:34PM -0800, Greg KH wrote:
> On Thu, Jan 06, 2005 at 03:26:21PM -0800, Andrew Morton wrote:
> > Which begs the question "how do we ever get rid of these things when we
> > have no projected date for Linux-2.8"?
> > 
> > I'd propose:
> > 
> > a) Create Documentation/feature-removal-schedule.txt which describes
> >    things which are going away, when, why, who is involved, etc.
> 
> Ok, I'll bite, here's a patch that does just that.  Look good?
> 
> thanks,
> 
> greg k-h
> 
> -----------
> 
> Add Documentation/feature-removal-schedule.txt as a way to notify
> everyone when and what is going to be removed.
> 
> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
> 
> diff -Nru a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> --- /dev/null	Wed Dec 31 16:00:00 196900
> +++ b/Documentation/feature-removal-schedule.txt	2005-01-06 15:54:40 -08:00
> @@ -0,0 +1,17 @@
> +The following is a list of files and features that are going to be
> +removed in the kernel source tree.  Every entry should contain what
> +exactly is going away, why it is happening, and who is going to be doing
> +the work.  When the feature is removed from the kernel, it should also
> +be removed from this file.
> +
> +---------------------------
> +
> +What:	devfs
> +When:	July 2005
> +Files:	fs/devfs/*, include/linux/devfs_fs*.h and assorted devfs
> +	function calls throughout the kernel tree
> +Why:	It has been unmaintained for a number of years, has unfixable
> +	races, contains a naming policy within the kernel that is
> +	against the LSB, and can be replaced by using udev.
> +Who:	Greg Kroah-Hartman <greg@kroah.com>
> +

And another.  I would also like to flag the exports themselves as
indicated in the patch below.  Thoughts?

						Thanx, Paul

What:	call_rcu(), call_rcu_bh(), and synchronize_kernel() change from
	EXPORT_SYMBOL() to EXPORT_SYMBOL_GPL().
When:	January 9, 2006
Files:  kernel/rcupdate.c
Why:	There are no known environments supporting RCU from which
	one could reasonably expect to port a non-GPL kernel module
	or driver to Linux.
Who:	Paul E. McKenney <paulmck@us.ibm.com>


diff -urpN -X ../dontdiff linux-2.5/kernel/rcupdate.c linux-2.5-rcu-export-warn/kernel/rcupdate.c
--- linux-2.5/kernel/rcupdate.c	Sat Jan  8 09:25:55 2005
+++ linux-2.5-rcu-export-warn/kernel/rcupdate.c	Sat Jan  8 10:21:18 2005
@@ -465,6 +465,8 @@ void synchronize_kernel(void)
 }
 
 module_param(maxbatch, int, 0);
+
+/* WARNING: these will become EXPORT_SYMBOL_GPL() in January 2006. */
 EXPORT_SYMBOL(call_rcu);
 EXPORT_SYMBOL(call_rcu_bh);
 EXPORT_SYMBOL(synchronize_kernel);

  parent reply	other threads:[~2005-01-08 18:32 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:05 [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-06 19:13 ` Christoph Hellwig
2005-01-06 20:07   ` Paul E. McKenney
2005-01-06 20:13     ` Christoph Hellwig
2005-01-06 20:35   ` Mike Waychison
2005-01-06 20:59     ` Christoph Hellwig
2005-01-06 21:35       ` Greg KH
2005-01-06 19:14 ` Al Viro
2005-01-06 20:13   ` Paul E. McKenney
2005-01-06 19:20 ` Arjan van de Ven
2005-01-06 20:15   ` Paul E. McKenney
2005-01-06 20:32     ` Al Viro
2005-01-06 21:04       ` Paul E. McKenney
2005-01-06 21:24         ` Al Viro
2005-01-06 23:26           ` Andrew Morton
2005-01-06 23:11             ` Alan Cox
2005-01-07  0:24               ` Linus Torvalds
2005-01-07  0:48                 ` Christoph Hellwig
2005-01-07  7:38                 ` Arjan van de Ven
2005-01-06 23:41             ` Christoph Hellwig
2005-01-07  0:29               ` Andrew Morton
2005-01-07  0:26                 ` Christoph Hellwig
2005-01-07  3:30                   ` Mike Waychison
2005-01-07  9:00                   ` Ingo Molnar
2005-01-07  9:15                     ` Christoph Hellwig
2005-01-07 12:14                       ` Antonio Vargas
2005-01-07 22:00                       ` Andrew Morton
2005-01-07 22:19                         ` Christoph Hellwig
2005-01-07 22:58                           ` Andrew Morton
2005-01-08 15:45                             ` Alan Cox
2005-01-07 22:49                         ` Alan Cox
2005-01-08  0:12                           ` Andrew Morton
2005-01-08  2:20                             ` Paul E. McKenney
2005-01-07 23:32                         ` Adrian Bunk
2005-01-08 13:10                           ` Al Viro
2005-01-07  1:34                 ` Alan Cox
2005-01-07  3:17                   ` Andrew Morton
2005-01-07  8:12                     ` Christoph Hellwig
2005-01-06 23:56             ` [PATCH] add feature-removal-schedule.txt documentation Greg KH
2005-01-07  0:23               ` Christoph Hellwig
2005-01-07  0:32                 ` Greg KH
2005-01-07 17:02               ` Randy.Dunlap
2005-01-07 17:54                 ` Linus Torvalds
2005-01-07 18:11                   ` Greg KH
2005-01-11 12:23                     ` [PATCH] cpufreq 2.4 interface removal schedule [Was: Re: [PATCH] add feature-removal-schedule.txt documentation] Dominik Brodowski
2005-01-12 18:41                       ` Greg KH
2005-01-07 23:58                 ` [PATCH] add feature-removal-schedule.txt documentation Dominik Brodowski
2005-01-12 18:41                 ` Greg KH
2005-01-08 18:32               ` Paul E. McKenney [this message]
2005-01-08 21:46                 ` Alan Cox
2005-01-08 23:03                   ` Arjan van de Ven
2005-01-09  6:23                     ` Paul E. McKenney
2005-01-09  6:27                   ` Paul E. McKenney
2005-01-07  2:02             ` [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-07  1:01           ` Paul E. McKenney
2005-01-07  1:20             ` Al Viro
2005-01-13  2:51             ` Paul E. McKenney
2005-01-13  7:35               ` Arjan van de Ven
2005-01-13 17:53                 ` Paul E. McKenney
2005-01-13 17:07               ` Greg KH
2005-01-13 17:44                 ` Paul E. McKenney
2005-01-13 17:55                   ` Greg KH
2005-01-13 18:29                     ` Paul E. McKenney
2005-01-07  7:33         ` Arjan van de Ven
2005-01-07  8:15           ` Christoph Hellwig
2005-01-07 15:12           ` Paul E. McKenney
2005-01-07 15:23             ` Arjan van de Ven
2005-01-07 15:34               ` Paul E. McKenney
2005-01-07 15:56                 ` Arjan van de Ven

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=20050108183220.GA2033@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=dipankar@in.ibm.com \
    --cc=greg@kroah.com \
    --cc=greghk@us.ibm.com \
    --cc=jtk@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markv@us.ibm.com \
    --cc=pbadari@us.ibm.com \
    --cc=torvalds@osdl.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=wtaber@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).