Closed rilcal closed 5 months ago
It is not so easy and would be misleading. The actual sllin.c kernel module is GPL-2.0-or-later at this moment. The tools are GPL-2.0-or-later or BSD-3-Clause. The BSD has been added because some company send request that they want to integrate configuration into their application (as I know, proprietary).
So adding LGPL2 at the to of the project contradicts to the kernel module license and even tools license, and on the other hand narrows tools license which is more permissive when BSD option is taken.
What is your need to add single license to the whole project?
I agree that there could help adding a top level README.md to the the top of the repository with information that kernel module and its README is in the sllin
subdirectory and that tool is in another subdirectory and is available even as the code fragment for proprietary programs which use GPL2+ code through separation of kernel API.
Thank you for getting back on this so quickly. It seems as though there was a misunderstanding on my team on the need for an explicit license file. With your explanation we were able to work through the understanding. This PR is no longer necessary. Thanks again!
In order to explicitly know how and where I can use this kernel module, I recommend adding a license file to this repository. This PR simply adds the GNU Lesser General Public License to this repository.