The shorthand `GPLv2+` and `LGPLv2.1+` got me as I was writing the meson
build, even though I was fully aware of the correct license.
Use the full SPDX identifier throughout the project - aka update the two
documents to align with the rest of the project.
Reference:
ca9a7f4c ("build: Fix license specification")
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Reviewed-by: Lucas De Marchi <demarchi@kernel.org>
Link: https://github.com/kmod-project/kmod/pull/pull/417
Signed-off-by: Lucas De Marchi <demarchi@kernel.org>
## License and SPDX
-The project uses `GPLv2+` for `tools/` and `LGPLv2.1+` for everything else.
-New tools should be licensed under `LGPLv2.1+` to make it easy to migrate code
-to other places when/if needed. When adding new files use the respective
-`SPDX-License-Identifier:` instead of the complete license text.
+The project uses `GPL-2.0-or-later` for `tools/` and `LGPL-2.1-or-later` for
+everything else. New tools should be licensed under `LGPL-2.1-or-later` to make
+it easy to migrate code to other places when/if needed. When adding new files
+use the respective `SPDX-License-Identifier:` instead of the complete license
+text.
## Commit style and history
- Mirror: <https://kernel.googlesource.com/pub/scm/utils/kernel/kmod/kmod.git>
- License:
- - LGPLv2.1+ for libkmod, testsuite and helper libraries
- - GPLv2+ for tools/*
+ - `LGPL-2.1-or-later` for libkmod, testsuite and helper libraries
+ - `GPL-2.0-or-later` for tools/
- Irc: `#kmod` on irc.oftc.net