From: Jonathan Corbet <corbet@lwn.net>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spdx@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH] docs/licensing: Clarify wording about "GPL" and "Proprietary"
Date: Fri, 22 Nov 2024 10:45:43 -0700 [thread overview]
Message-ID: <87iksf2md4.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20241115103842.585207-2-ukleinek@kernel.org>
Uwe Kleine-König <ukleinek@kernel.org> writes:
> There are currently some doubts about out-of-tree kernel modules licensed
> under GPLv3 and if they are supposed to be able to use symbols exported
> using EXPORT_SYMBOL_GPL.
>
> Clarify that "Proprietary" means anything non-GPL2 even though the
> license might be an open source license. Also disambiguate "GPL
> compatible" to "GPLv2 compatible".
>
> Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
> ---
> Hello,
>
> these are the locations that I found by a quick grep. If you spot a
> document that needs similar updating, please tell.
>
> The change in license-rules.rst looks bigger than it actually is due to
> changing where the line wrappings occur. With `git diff --word-diff` it
> reduces to:
>
> "Proprietary" The module is under a proprietary license.
> {+"Proprietary" is to be understood only as+}
> {+ "The license is not compatible to GPLv2".+}
> This string is solely for [-proprietary-]{+non-GPL2 compatible+}
> third party modules and cannot be used for
>
> Best regards
> Uwe
>
> Documentation/kernel-hacking/hacking.rst | 2 +-
> Documentation/process/license-rules.rst | 18 ++++++++++--------
> 2 files changed, 11 insertions(+), 9 deletions(-)
There seem to be no objections, so I've applied this.
Thanks,
jon
prev parent reply other threads:[~2024-11-22 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 10:38 [PATCH] docs/licensing: Clarify wording about "GPL" and "Proprietary" Uwe Kleine-König
2024-11-15 11:11 ` Werner Sembach
2024-11-22 17:45 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iksf2md4.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ukleinek@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox