From: Greg KH <greg@kroah.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
paul.mckenney@us.ibm.com, linux-usb-devel@lists.sourceforge.net
Subject: Re: [patch 01/03] add EXPORT_SYMBOL_GPL_FUTURE()
Date: Wed, 8 Feb 2006 14:57:33 -0800 [thread overview]
Message-ID: <20060208225733.GA28826@kroah.com> (raw)
In-Reply-To: <20060208201645.GA9497@mars.ravnborg.org>
On Wed, Feb 08, 2006 at 09:16:45PM +0100, Sam Ravnborg wrote:
> On Wed, Feb 08, 2006 at 08:49:26PM +0100, Sam Ravnborg wrote:
> > On Wed, Feb 08, 2006 at 10:49:22AM -0800, Greg KH wrote:
> > > This patch adds the ability to mark symbols that will be changed in the
> > > future, so that non-GPL usage of them is flagged by the kernel and
> > > printed out to the system log.
> > >
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > The patch duplicate too much code to my taste at least.
> > May I suggest to consolidate a little in module.c before applying the
> > GPL_FUTURE stuff.
> >
> > Have you considered: EXPORT_GPL_SOON()?
Well, as I'm proposing that the USB symbols be converted in 2 years,
that's not exactly "SOON" :)
> Better version below...
Very nice, I've added this to my tree. I had originally tried to do
something like this, but your version is very nice compared to my bad
hack.
thanks,
greg k-h
prev parent reply other threads:[~2006-02-08 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 18:48 [patch 00/03] EXPORT_SYMBOL_GPL_FUTURE() Greg KH
2006-02-08 18:49 ` [patch 01/03] add EXPORT_SYMBOL_GPL_FUTURE() Greg KH
2006-02-08 18:50 ` [patch 02/03] add EXPORT_SYMBOL_GPL_FUTURE() to RCU subsystem Greg KH
2006-02-08 18:51 ` [patch 03/03] add EXPORT_SYMBOL_GPL_FUTURE() to USB subsystem Greg KH
2006-02-08 19:31 ` [patch 02/03] add EXPORT_SYMBOL_GPL_FUTURE() to RCU subsystem Dipankar Sarma
2006-02-08 19:40 ` Greg KH
2006-02-08 19:49 ` [patch 01/03] add EXPORT_SYMBOL_GPL_FUTURE() Sam Ravnborg
2006-02-08 20:16 ` Sam Ravnborg
2006-02-08 22:57 ` Greg KH [this message]
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=20060208225733.GA28826@kroah.com \
--to=greg@kroah.com \
--cc=dipankar@in.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=paul.mckenney@us.ibm.com \
--cc=sam@ravnborg.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