Messages in this thread | | | From | "David McIlwraith" <> | Subject | Re: spinlocks, the GPL, and binary-only modules | Date | Wed, 20 Nov 2002 14:03:08 +1100 |
| |
Ugh. Seems I misunderstood; I didn't note the reference to binary modules. ----- Original Message ----- From: "David McIlwraith" <quack@bigpond.net.au> To: <linux-kernel@vger.kernel.org> Sent: Wednesday, November 20, 2002 1:49 PM Subject: Re: spinlocks, the GPL, and binary-only modules
> How should it? The compiler (specifically, the C preprocessor) includes the > code, thus it is not the AUTHOR violating the GPL. > > ----- Original Message ----- > From: "Rik van Riel" <riel@conectiva.com.br> > To: "Jeff Garzik" <jgarzik@pobox.com> > Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org> > Sent: Wednesday, November 20, 2002 12:52 PM > Subject: Re: spinlocks, the GPL, and binary-only modules > > > > On Tue, 19 Nov 2002, Jeff Garzik wrote: > > > > > So, since spinlocks and semaphores are (a) inline and #included into > > > your code, and (b) required for just about sane interoperation with > Linux... > > > > > > does this mean that all binary-only modules that #include kernel code > > > such as spinlocks are violating the GPL? > > > > > But who knows if #include'd code constitutes a derived work :( > > > > Only if the #included snippets of code are large enough to be > > protected by copyright, which might be true of the stuff in > > mm_inline.h and of some of the semaphore code, but probably > > isn't true of the spinlock code. > > > > Even if the code #included is large enough to be protected by > > copyright I don't know if the code including it would be considered > > a derived work. Many questions remaining... > > > > regards, > > > > Rik > > -- > > Bravely reimplemented by the knights who say "NIH". > > http://www.surriel.com/ http://guru.conectiva.com/ > > Current spamtrap: <a > href=mailto:"october@surriel.com">october@surriel.com</a> > > > > - > > 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/ >
- 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/
| |