1
0
Fork 0

doc: process: GPL -> GPL-compatible

Drivers under MIT, BSD-17-clause, or uncle-Bob's-newest-take-on-PD are
all fine, not just GPL.

Signed-off-by: Adam Borowski <kilobyte@angband.pl>
[jc: fixed conflict and refilled paragraph]
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
hifive-unleashed-5.1
Adam Borowski 2019-01-22 10:34:08 +01:00 committed by Jonathan Corbet
parent a41e8f25fa
commit 8f7e6d134b
1 changed files with 7 additions and 7 deletions

View File

@ -169,13 +169,13 @@ driver for every different kernel version for every distribution is a
nightmare, and trying to keep up with an ever changing kernel interface nightmare, and trying to keep up with an ever changing kernel interface
is also a rough job. is also a rough job.
Simple, get your kernel driver into the main kernel tree (remember we Simple, get your kernel driver into the main kernel tree (remember we are
are talking about GPL released drivers here, if your code doesn't fall talking about drivers released under a GPL-compatible license here, if your
under this category, good luck, you are on your own here, you leech). If your code doesn't fall under this category, good luck, you are on your own here,
driver is in the tree, and a kernel interface changes, it will be fixed you leech). If your driver is in the tree, and a kernel interface changes,
up by the person who did the kernel change in the first place. This it will be fixed up by the person who did the kernel change in the first
ensures that your driver is always buildable, and works over time, with place. This ensures that your driver is always buildable, and works over
very little effort on your part. time, with very little effort on your part.
The very good side effects of having your driver in the main kernel tree The very good side effects of having your driver in the main kernel tree
are: are: