public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Takashi Iwai <tiwai@suse.de>, SeongJae Park <sj@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-doc@vger.kernel.org,
	Takashi Iwai <tiwai@suse.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 8/8] Docs/sound/index: Add missing SPDX License Identifier
Date: Tue, 24 Jan 2023 15:04:45 -0700	[thread overview]
Message-ID: <87r0vjfv2a.fsf@meer.lwn.net> (raw)
In-Reply-To: <268823a3-f453-a38b-3fd7-500306675890@linux.intel.com>

Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> writes:

> On 1/23/23 02:10, Takashi Iwai wrote:
>> On Sun, 22 Jan 2023 22:36:50 +0100,
>> SeongJae Park wrote:
>>>
>>> Add missing SPDX License Identifier for sound documentation index file.
>>>
>>> Signed-off-by: SeongJae Park <sj@kernel.org>
>> 
>> Acked-by: Takashi Iwai <tiwai@suse.de>
>
> Isn't GPL-2.0 deprecated? It should be GPL-2.0-only, no?
>
> https://spdx.org/licenses/GPL-2.0.html
>
> https://spdx.org/licenses/GPL-2.0-only.html

The kernel community hasn't really followed along with that change on
the part of the SPDX folks; as far as I know, GPL-2.0 is considered to
be just fine.  There are currently more than twice as many GPL-2.0
declarations than GPL-2.0-only.

Thanks,

jon

  reply	other threads:[~2023-01-24 22:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 21:36 [PATCH v2 0/8] Docs: Add missing SPDX license identifiers of SeongJae Park
2023-01-22 21:36 ` [PATCH v2 1/8] Docs/crypto/index: Add missing SPDX License Identifier SeongJae Park
2023-01-22 21:36 ` [PATCH v2 2/8] Docs/driver-api/index: " SeongJae Park
2023-01-22 21:36 ` [PATCH v2 3/8] Docs/gpu/index: " SeongJae Park
2023-01-22 21:36 ` [PATCH v2 4/8] Docs/hwmon/index: " SeongJae Park
2023-01-24 13:49   ` Guenter Roeck
2023-01-31  3:44   ` Guenter Roeck
2023-01-31 14:44     ` Jonathan Corbet
2023-01-31 14:51       ` Mauro Carvalho Chehab
2023-01-31 14:48   ` Mauro Carvalho Chehab
2023-01-31 15:02   ` Guenter Roeck
2023-01-22 21:36 ` [PATCH v2 5/8] Docs/input/index: " SeongJae Park
2023-01-31 14:57   ` Mauro Carvalho Chehab
2023-01-22 21:36 ` [PATCH v2 6/8] Docs/mm/index: " SeongJae Park
2023-01-22 21:36 ` [PATCH v2 7/8] Docs/scheduler/index: " SeongJae Park
2023-01-31 14:58   ` Mauro Carvalho Chehab
2023-01-22 21:36 ` [PATCH v2 8/8] Docs/sound/index: " SeongJae Park
2023-01-23  8:10   ` Takashi Iwai
2023-01-23 16:02     ` Pierre-Louis Bossart
2023-01-24 22:04       ` Jonathan Corbet [this message]
2023-01-23 15:02 ` [PATCH v2 0/8] Docs: Add missing SPDX license identifiers of Jonathan Corbet
2023-01-24 22:31 ` Jonathan Corbet
2023-01-24 23:03   ` SeongJae Park

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=87r0vjfv2a.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sj@kernel.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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