[lkml]   [2006]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: incorrect taint of ndiswrapper
Ar Iau, 2006-10-26 am 15:41 +0100, ysgrifennodd Al Viro:
> Could we please decide WTF _GPLONLY *is* and at least remain consistent?
> Aside of "method of fighting binary-only modules", that is - this part
> is obvious.

It was originally added to mark symbols that are clearly internal only
and make a work derivative. It's somewhere expanded to include symbols
whose code authors think that a cease and desist is the correct answer
to non GPL use.

I can't really help personally on the details there since I'm of the
opinion that _GPLONLY while useful doesn't generally make a blind bit of
difference as most if not all binary modules are violating the license.
(And I'm sure Nvidia's legal counsel disagrees with me at least in


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-10-26 16:55    [W:0.087 / U:5.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site