summaryrefslogtreecommitdiff
path: root/Documentation/process
diff options
context:
space:
mode:
authorAdam Borowski <kilobyte@angband.pl>2019-01-22 12:34:08 +0300
committerJonathan Corbet <corbet@lwn.net>2019-02-02 02:19:11 +0300
commit8f7e6d134bda563c9b3abac14de11e89eb4c86d7 (patch)
treec92396fd4b9541891f7a6859021f34bfc2121942 /Documentation/process
parenta41e8f25fa8f8f67360d88eb0eebbabe95a64bdf (diff)
downloadlinux-8f7e6d134bda563c9b3abac14de11e89eb4c86d7.tar.xz
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>
Diffstat (limited to 'Documentation/process')
-rw-r--r--Documentation/process/stable-api-nonsense.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/process/stable-api-nonsense.rst b/Documentation/process/stable-api-nonsense.rst
index 57d95a49c096..a9625ab1fdc2 100644
--- a/Documentation/process/stable-api-nonsense.rst
+++ b/Documentation/process/stable-api-nonsense.rst
@@ -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
is also a rough job.
-Simple, get your kernel driver into the main kernel tree (remember we
-are talking about GPL released drivers here, if your code doesn't fall
-under this category, good luck, you are on your own here, you leech). If your
-driver is in the tree, and a kernel interface changes, it will be fixed
-up by the person who did the kernel change in the first place. This
-ensures that your driver is always buildable, and works over time, with
-very little effort on your part.
+Simple, get your kernel driver into the main kernel tree (remember we are
+talking about drivers released under a GPL-compatible license here, if your
+code doesn't fall under this category, good luck, you are on your own here,
+you leech). If your driver is in the tree, and a kernel interface changes,
+it will be fixed up by the person who did the kernel change in the first
+place. This ensures that your driver is always buildable, and works over
+time, with very little effort on your part.
The very good side effects of having your driver in the main kernel tree
are: