From: "Piotr Masłowski" <piotr@maslowski.xyz>
To: "Tim Bird" <tim.bird@sony.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <povik+lin@cutebit.org>,
<david.rhodes@cirrus.com>, <rf@opensource.cirrus.com>,
<cezary.rojewski@intel.com>, <peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>,
<ranjani.sridharan@linux.intel.com>,
<kai.vehmanen@linux.intel.com>, <linux-spdx@vger.kernel.org>,
<asahi@lists.linux.dev>, <patches@opensource.cirrus.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sound: soc: Add SPDX ids to many soc files
Date: Tue, 17 Feb 2026 16:51:54 +0100 [thread overview]
Message-ID: <DGHCVCRACU6X.2KYOL2RQWEUG7@maslowski.xyz> (raw)
In-Reply-To: <20260214004314.3787727-1-tim.bird@sony.com>
Hello!
On Sat Feb 14, 2026 at 1:43 AM CET, Tim Bird wrote:
> Add appropriate SPDX-License-Identifier lines to the
> the remaining files that are missing such lines in the
> sound/soc directory, and in a few other miscelaneous files.
> Remove boilerplate license text.
>
[...]
> +# SPDX-License-Identifier: GPL-2.0-only
[...]
> +# SPDX-License-Identifier: GPL-2.0
Is there some intended meaning behind this distinction? Bear in mind
I'm not a kernel developer so I might very well be missing something,
but AFAIK the `GPL-2.0` SPDX identifier is just an older, deprecated
variant with the same meaning as `GPL-2.0-only`. (Just like `GPL-2.0+`
which is a deprecated version of `GPL-2.0-or-later`.)
Anyway, this patch looks like a nice improvement.
[...]
Best regards,
Piotr Masłowski
next prev parent reply other threads:[~2026-02-17 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 0:43 Tim Bird
2026-02-17 15:51 ` Piotr Masłowski [this message]
2026-02-17 16:26 ` Richard Fontana
2026-02-17 17:32 ` Piotr Masłowski
2026-02-17 18:10 ` Bird, Tim
2026-02-17 18:21 ` Mark Brown
2026-02-17 18:32 ` Bird, Tim
2026-02-17 18:55 ` Mark Brown
2026-02-17 18:49 ` Piotr Masłowski
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=DGHCVCRACU6X.2KYOL2RQWEUG7@maslowski.xyz \
--to=piotr@maslowski.xyz \
--cc=asahi@lists.linux.dev \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=david.rhodes@cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=povik+lin@cutebit.org \
--cc=ranjani.sridharan@linux.intel.com \
--cc=rf@opensource.cirrus.com \
--cc=tim.bird@sony.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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®