lkml.org 
[lkml]   [2001]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: GPLONLY kernel symbols???
John Levon writes:
> On Wed, Oct 17, 2001 at 12:17:39PM +1000, Keith Owens wrote:
>
> > If a symbol has been exported with EXPORT_SYMBOL_GPL then it appears as
> > unresolved for modules that do not have a GPL compatible MODULE_LICENCE
> > string. So when a module without a GPL compatible MODULE_LICENCE gets
> > an unresolved symbol, I print that message as a hint to the user. I
> > thought the response was obvious, but looks like I need to expand the
> > hint text even further.
>
> How is the name mangled in the _GPL case ? Can't this be detected explicitly ?
>
> richard, since ac seems OK with it ...

OK, I've applied your patch. Let's hope lusers don't start editing out
the "tainted" string when emailing Oops reports.

BTW: I had to edit after applying your patch: it didn't conform to the
Style[tm].

Regards,

Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.101 / U:11.340 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site