From: Greg KH <greg@kroah.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org,
Ram Pai <linuxram@us.ibm.com>
Subject: Re: GPL-only symbols issue
Date: Mon, 8 May 2006 21:25:00 -0700 [thread overview]
Message-ID: <20060509042500.GA4226@kroah.com> (raw)
In-Reply-To: <445F0B6F.76E4.0078.0@novell.com>
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.
thanks,
greg k-h
next prev parent reply other threads:[~2006-05-09 4:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 7:12 GPL-only symbols issue Jan Beulich
2006-05-08 20:23 ` Sam Ravnborg
2006-05-09 4:25 ` Greg KH [this message]
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 ` GPL-only symbols issue Sam Ravnborg
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=20060509042500.GA4226@kroah.com \
--to=greg@kroah.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@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