public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EXPORT_SYMBOL_GPL_FUTURE()
Date: Wed, 8 Feb 2006 09:42:24 -0800	[thread overview]
Message-ID: <20060208174224.GD14105@suse.de> (raw)
In-Reply-To: <1139408629.26270.38.camel@localhost.localdomain>

On Wed, Feb 08, 2006 at 02:23:49PM +0000, Alan Cox wrote:
> On Maw, 2006-02-07 at 22:20 -0800, Greg KH wrote:
> > Currently we don't have a way to show people that some kernel symbols
> > will be changed in the future from EXPORT_SYMBOL() to
> > EXPORT_SYMBOL_GPL(). 
> 
> For a good reason. When Linus first accepted the _GPL changes he did so
> on the clear understanding that people wouldn't go around "privatising" 
> existing symbols.

But look at Documentation/feature-removal-schedule.txt:

	What:   RCU API moves to EXPORT_SYMBOL_GPL
	When:   April 2006
	Files:  include/linux/rcupdate.h, kernel/rcupdate.c
	Why:    Outside of Linux, the only implementations of anything even
	        vaguely resembling RCU that I am aware of are in DYNIX/ptx,
	        VM/XA, Tornado, and K42.  I do not expect anyone to port binary
	        drivers or kernel modules from any of these, since the first two
	        are owned by IBM and the last two are open-source research OSes.
	        So these will move to GPL after a grace period to allow
	        people, who might be using implementations that I am not aware
	        of, to adjust to this upcoming change.
	Who:    Paul E. McKenney <paulmck@us.ibm.com>


That's just one example.

The other example, and is what just happened last week, is for the USB
api.  We have changed enough over the years to cause a new function
call to be created, yet we offered a inline function to help with the
transition.  That new function was marked EXPORT_SYMBOL_GPL() as the USB
developers feel there has been enough change to warrant this marking.
Also because they provide a way for userspace USB drivers to be written
for those that want to do closed source stuff.

So, no matter how it is marked in this text file, people will miss it.
If we complain in the syslog, it makes it very hard to miss it, and will
allow people notice to be able to port stuff properly.

In short, due to the lack of the "unstable/stable" series cycle, we
don't have a method to mark stuff GPL only that will give enough
exposure.  This patch provides it.

I'll repost the series based on the comments in this thread, and stuff
that others have sent me privately.

thanks,

greg k-h

  reply	other threads:[~2006-02-08 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  6:20 [RFC] EXPORT_SYMBOL_GPL_FUTURE() Greg KH
2006-02-08  7:33 ` Andrew Morton
2006-02-08 17:36   ` Greg KH
2006-02-08 14:23 ` Alan Cox
2006-02-08 17:42   ` Greg KH [this message]
2006-02-08 18:38     ` Alan Cox
2006-02-12  2:34 ` Mark Lord
2006-02-12  4:15   ` Greg KH
2006-02-12  4:18     ` Mark Lord
2006-02-22  5:39       ` Greg KH
2006-02-12  4:41     ` Kyle Moffett

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=20060208174224.GD14105@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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