@sun @scathach The macro is MODULE_LICENSE and the only string the macro really accepts is "GPL" and it seems those Linux developers haven't read the GPLv2;
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

The driver was erroneously advertising it was any version, when it was GPLv3-or-later seemingly.

There wouldn't have been any issues if many Linux developers didn't maliciously license GPLv2-only.


The hypocrisy of the Linux developers was of course enormous, considering that they're okay with proprietary modules, but free modules under a free license that better respects the users freedom are unacceptable?


Nothing was fixed - rather the modules were added into a module blacklist, which was inane considering that they were in the process of getting the modules re-licensed to GPLv2-or-later.