mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg KH <greg@kroah.com>
Cc: Jan Beulich <jbeulich@novell.com>,
	linux-kernel@vger.kernel.org, Ram Pai <linuxram@us.ibm.com>
Subject: Re: GPL-only symbols issue
Date: Sat, 17 Jun 2006 23:06:50 +0200	[thread overview]
Message-ID: <20060617210650.GA9243@mars.ravnborg.org> (raw)
In-Reply-To: <20060509042500.GA4226@kroah.com>

On Mon, May 08, 2006 at 09:25:00PM -0700, Greg KH wrote:
> On Mon, May 08, 2006 at 09:12:15AM +0200, Jan Beulich wrote:
> > Sam,
> > 
> > would it seem reasonable a request to detect imports of GPL-only
> > symbols by non-GPL modules also at build time rather than only at run
> > time, and at least warn about such?
> 
> Ram has some tools that might catch this kind of thing.  He's posted his
> scripts to lkml in the past, try looking in the archives.

Responding to an old post here.

I have only recently integrated Ram's patches except for the kbuild
integration bits. On top of this Andreas' license compatibility thing so
in effect:
building a GPL module (or compatible) => no change
building a GPL-incompatible module =>
                           warn if module uses EXPORT_SYMBOL_GPL_FUTURE
                           error out if module uses EXPORT_SYMBOL_GPL

Patches are in kbuild.git.
The script to show module export statistics is not yet merged, I've
asked Ram to fix a few things first.

	Sam

      parent reply	other threads:[~2006-06-17 21:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  7:12 Jan Beulich
2006-05-08 20:23 ` Sam Ravnborg
2006-05-09  4:25 ` Greg KH
2006-05-09  5:57   ` Ram Pai
2006-05-09 13:11     ` Philip R. Auld
2006-05-09 17:31     ` Andreas Gruenbacher
2006-05-09 17:31     ` [PATCH] Check for license compliance at build time Andreas Gruenbacher
2006-05-09 20:55       ` Ram Pai
2006-05-09 22:24         ` Sam Ravnborg
2006-06-17 21:06   ` Sam Ravnborg [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=20060617210650.GA9243@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=greg@kroah.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@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

Powered by JetHome