public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Diederik de Haas <didi.debian@cknow.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"open list:MODULE SUPPORT" <linux-modules@vger.kernel.org>,
	"open list:MODULE SUPPORT" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] module.h: Fix full name of the GPL
Date: Tue, 24 Jan 2023 09:49:02 +0700	[thread overview]
Message-ID: <Y89HHtQQ4/pvsOut@debian.me> (raw)
In-Reply-To: <20230122193443.60267-1-didi.debian@cknow.org>

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

On Sun, Jan 22, 2023 at 08:34:43PM +0100, Diederik de Haas wrote:
> Signed-off-by: Diederik de Haas <didi.debian@cknow.org>

No patch description, really?

> ---
>  include/linux/module.h | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 8c5909c0076c..329fa0b56642 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -186,14 +186,14 @@ extern void cleanup_module(void);
>   * The following license idents are currently accepted as indicating free
>   * software modules
>   *
> - *	"GPL"				[GNU Public License v2]
> - *	"GPL v2"			[GNU Public License v2]
> - *	"GPL and additional rights"	[GNU Public License v2 rights and more]
> - *	"Dual BSD/GPL"			[GNU Public License v2
> + *	"GPL"				[GNU General Public License v2]
> + *	"GPL v2"			[GNU General Public License v2]
> + *	"GPL and additional rights"	[GNU General Public License v2 rights and more]
> + *	"Dual BSD/GPL"			[GNU General Public License v2
>   *					 or BSD license choice]
> - *	"Dual MIT/GPL"			[GNU Public License v2
> + *	"Dual MIT/GPL"			[GNU General Public License v2
>   *					 or MIT license choice]
> - *	"Dual MPL/GPL"			[GNU Public License v2
> + *	"Dual MPL/GPL"			[GNU General Public License v2
>   *					 or Mozilla license choice]
>   *
>   * The following other idents are available

Why did you do that? Maybe as justification for your other GPL name expansion
fix patches? 

Anyway, let's see what Linus thinks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-01-24  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 19:34 [PATCH] module.h: Fix full name of the GPL Diederik de Haas
2023-01-24  2:49 ` Bagas Sanjaya [this message]
2023-01-24 13:32   ` Diederik de Haas
2023-01-24 14:09     ` Bagas Sanjaya
2023-01-24 17:36     ` Luis Chamberlain

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=Y89HHtQQ4/pvsOut@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=didi.debian@cknow.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=torvalds@linux-foundation.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