From: Greg KH <gregkh@linuxfoundation.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: mention MIT license as a compatible license with GPLv2
Date: Thu, 24 Jul 2025 12:38:24 +0200 [thread overview]
Message-ID: <2025072459-tweezers-dingbat-b748@gregkh> (raw)
In-Reply-To: <PN3PR01MB95977C87764A556FFD49FB72B85EA@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
On Thu, Jul 24, 2025 at 10:03:41AM +0000, Aditya Garg wrote:
> MIT is a widely used permissive free software license that is compatible
> with the GPLv2 license. This change adds it to the list of compatible
> licenses with GPLv2 in the kernel documentation.
No, please don't. This isn't a proper place for talking about the
different license interactions.
>
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
> ---
> Documentation/process/1.Intro.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/process/1.Intro.rst b/Documentation/process/1.Intro.rst
> index 25ca49f7a..c3465e3aa 100644
> --- a/Documentation/process/1.Intro.rst
> +++ b/Documentation/process/1.Intro.rst
> @@ -235,9 +235,9 @@ code must be compatible with version 2 of the GNU General Public License
> (GPLv2), which is the license covering the kernel distribution as a whole.
> In practice, that means that all code contributions are covered either by
> GPLv2 (with, optionally, language allowing distribution under later
> -versions of the GPL) or the three-clause BSD license. Any contributions
> -which are not covered by a compatible license will not be accepted into the
> -kernel.
> +versions of the GPL), the three-clause BSD license or the MIT license.
You forgot a ',' anyway :(
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-24 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 10:03 Aditya Garg
2025-07-24 10:38 ` Greg KH [this message]
2025-07-24 10:41 ` Aditya Garg
2025-07-24 11:47 ` Greg KH
2025-07-24 17:29 ` Randy Dunlap
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=2025072459-tweezers-dingbat-b748@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gargaditya08@live.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.org \
/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