All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EXPORT_SYMBOL_GPL_FUTURE()
Date: Sat, 11 Feb 2006 23:18:06 -0500	[thread overview]
Message-ID: <43EEB6FE.7000701@rtr.ca> (raw)
In-Reply-To: <20060212041522.GA29935@suse.de>

Greg KH wrote:
> On Sat, Feb 11, 2006 at 09:34:40PM -0500, Mark Lord wrote:
>> Greg KH wrote:
>>> So, here's a patch that implements EXPORT_SYMBOL_GPL_FUTURE().  It
>>> basically says that some time in the future, this symbol is going to
>>> change and not be allowed to be called from non-GPL licensed kernel
>>> modules.
>> The wording and intent here are incorrect.
>>
>> All kernel modules are already *GPL licensed*,
>> whether the authors think so or not.
>>
>> So this patch (if it goes through), should be reworded
>> so as not to muddy those waters (as the above excerpt does).
> 
> Care to provide some text that you feel will be better?

Just something simple, like this rewording of your original post:

 >>> So, here's a patch that implements EXPORT_SYMBOL_GPL_FUTURE().  It
 >>> basically says that some time in the future, this symbol is going to
 >>> change and not be allowed to be called from
...kernel modules that don't include MODULE_LICENSE("GPL") in the source.

Cheers

  reply	other threads:[~2006-02-12  4:18 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
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 [this message]
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=43EEB6FE.7000701@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=gregkh@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.