mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn	 <lukas.bulwahn@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Simon Horman <horms@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Colin Ian King	 <colin.i.king@gmail.com>,
	Yu Jiaoliang <yujiaoliang@vivo.com>,
	WangYuli	 <wangyuli@uniontech.com>,
	linux-kernel@vger.kernel.org, Andy Whitcroft	 <apw@canonical.com>
Subject: Re: [PATCH 0/2] scripts/spelling.txt: add GPL-2.0+
Date: Sun, 15 Dec 2024 05:42:45 -0800	[thread overview]
Message-ID: <be6ab9045b893b25bd0cb27e100bd5905fdc9281.camel@perches.com> (raw)
In-Reply-To: <59832da1-34a6-42be-ba85-e86d05b9d29b@canonical.com>

On Sun, 2024-12-15 at 13:41 +0100, Heinrich Schuchardt wrote:
> On 12/15/24 11:51, Joe Perches wrote:
> > On Sun, 2024-12-15 at 03:51 +0100, Heinrich Schuchardt wrote:
> > > The correct SPDX identifier for the 'GNU General Public License v2.0 or
> > > later' is GPL-2.0-or-later.
> > 
> > I think this unnecessary as there's a separate script
> > to check the appropriate SPDX uses treewide and there
> > isn't a single existing use of "gpl-2.0+' in the tree.
> 
> Hello Joe,
> 
> In next-20241213 I find 5143 occurrences with
> 
> git grep -ni 'gpl-2\.0+' | wc -l

So no uses of 'gpl-2.0+' but many of 'GPL-2.0+'

And perhaps read this:

https://lore.kernel.org/all/CAHk-=wi2bdXuYhC9bd9FShtcf_u-6RUb3Qr_aXq3XtbCxR5NGQ@mail.gmail.com/

      reply	other threads:[~2024-12-15 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15  2:51 Heinrich Schuchardt
2024-12-15  2:51 ` [PATCH 1/2] checkpatch: allow special characters in spelling.txt Heinrich Schuchardt
2024-12-15  2:51 ` [PATCH 2/2] scripts/spelling.txt: add GPL-2.0+ Heinrich Schuchardt
2024-12-16  2:53   ` WangYuli
2024-12-15 10:51 ` [PATCH 0/2] " Joe Perches
2024-12-15 12:41   ` Heinrich Schuchardt
2024-12-15 13:42     ` Joe Perches [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=be6ab9045b893b25bd0cb27e100bd5905fdc9281.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=colin.i.king@gmail.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=horms@kernel.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=wangyuli@uniontech.com \
    --cc=yujiaoliang@vivo.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
all inboxes | Powered by JetHome®