linux-kernel - Re: [PATCH] doc: process: GPL -> GPL-compatible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 22 Jan 2019 11:23:44 +0100
From:   Greg KH <greg@...ah.com>
To:     Adam Borowski <kilobyte@...band.pl>
Cc:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] doc: process: GPL -> GPL-compatible

On Tue, Jan 22, 2019 at 10:34:08AM +0100, Adam Borowski wrote:
> 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@...band.pl>
> ---
> Not reformatting to fill lines, it'll semi-conflict with another patch
> that's been acked but not yet pushed.
> 
>  Documentation/process/stable-api-nonsense.rst | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/process/stable-api-nonsense.rst b/Documentation/process/stable-api-nonsense.rst
> index 24f5aeecee91..9b69fb08b65e 100644
> --- a/Documentation/process/stable-api-nonsense.rst
> +++ b/Documentation/process/stable-api-nonsense.rst
> @@ -170,7 +170,8 @@ 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
> +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
>  <insert link to leech comment from Andrew and Linus here>.)  If your
>  driver is in the tree, and a kernel interface changes, it will be fixed

Nice fix:

Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>