On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
Hello,That's why it is documented, to explain this very thing. Please don't
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
Hello,As already being implied by that commit message, this is sadly not an issue
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed under GPLv3 or later. This is incompatible with the
kernel's license and so makes it impossible for distributions and other
third parties to support these at least in pre-compiled form and so
limits user experience and the possibilities to work on mainlining these
drivers.
This incompatibility is created on purpose to control the upstream
process. Seehttps://fosstodon.org/@kernellogger/113423314337991594 for
a nice summary of the situation and some further links about the issue.
Note that the pull request that fixed the MODULE_LICENSE invocations to
stop claiming GPL(v2) compatibility was accepted and then immediately
reverted "for the time being until the legal stuff is sorted out"
(https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/commit/a8c09b6c2ce6393fe39d8652d133af9f06cfb427).
that can be sorted out over night.
We ended up in this situation as MODULE_LICENSE("GPL") on its own does not
hint at GPL v2, if one is not aware of the license definition table in the
documentation.
suggest that documenting this is somehow not providing a hint. That's
just not going to fly with any lawyer who reads any of this, sorry.
greg k-h