spinlocks, the GPL, and binary-only modules

Jeff Garzik (jgarzik@pobox.com)
Tue, 19 Nov 2002 17:09:49 -0500


blah.

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? IOW just about every binary
module out there, I would think...

I'm sure this would make extremeists happy, but I personally don't mind
binary-only modules as long as the binary-only code [ignoring the
#included kernel code] cannot be considered a derived work.

But who knows if #include'd code constitutes a derived work :(

Jeff

-
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/