workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-spdx@vger.kernel.org, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] LICENSES: Explicitly allow SPDX-FileCopyrightText
Date: Wed, 7 Jan 2026 21:29:29 +0200	[thread overview]
Message-ID: <20260107192929.GE20168@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2026010724-activate-saggy-9c08@gregkh>

On Wed, Jan 07, 2026 at 07:52:31PM +0100, Greg KH wrote:
> On Wed, Jan 07, 2026 at 06:12:47PM +0100, Krzysztof Kozlowski wrote:
> > Sources already have SPDX-FileCopyrightText (~40 instances) and more
> > appear on the mailing list, so document that it is allowed.  On the
> > other hand SPDX defines several other tags like SPDX-FileType, so add
> > checkpatch rule to narrow desired tags only to two of them - license and
> > copyright.  That way no new tags would sneak in to the kernel unnoticed.
> > 
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> > 
> > ---
> > 
> > Other way would be to remove SPDX-FileCopyrightText from existing files
> > and disallow this, but one way or another we should be explicit about
> > it.  Otherwise people will be sending more of these and each maintainer
> > would need to make their own call.
> > ---
> >  Documentation/process/license-rules.rst | 2 ++
> >  scripts/checkpatch.pl                   | 9 +++++++++
> >  2 files changed, 11 insertions(+)
> > 
> > diff --git a/Documentation/process/license-rules.rst b/Documentation/process/license-rules.rst
> > index 59a7832df7d0..8d7c0214f283 100644
> > --- a/Documentation/process/license-rules.rst
> > +++ b/Documentation/process/license-rules.rst
> > @@ -66,6 +66,8 @@ License identifier syntax
> >     '#!PATH_TO_INTERPRETER' in the first line.  For those scripts the SPDX
> >     identifier goes into the second line.
> 
> As you are adding a copyright identifier, this sentence should probably
> be:
> 	For those scripts, the SPDX license identifier goes into the
> 	second line.
> 
> > +   Identifier line can be followed by another one with SPDX-FileCopyrightText.
> 
> How about:
> 
> "The license identifier line can then be followed by a
> SPDX-FileCopyrightText line if desired."

I'd write "by one of multiple" instead of "by a" as multiple copyright
owners for the same file is common in the kernel.

> > +
> >  |
> >  
> >  2. Style:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 362a8d1cd327..98261ee97e2b 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -3844,6 +3844,15 @@ sub process {
> >  			     "Misplaced SPDX-License-Identifier tag - use line $checklicenseline instead\n" . $herecurr);
> >  		}
> >  
> > +# check for unused SPDX file tags
> 
> # check for unsupported SPDX file tags

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2026-01-07 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 17:12 Krzysztof Kozlowski
2026-01-07 18:40 ` Joe Perches
2026-01-07 19:35   ` Greg Kroah-Hartman
2026-01-07 19:38     ` Joe Perches
2026-01-07 21:28       ` Krzysztof Kozlowski
2026-01-07 18:52 ` Greg Kroah-Hartman
2026-01-07 19:29   ` Laurent Pinchart [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=20260107192929.GE20168@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=tglx@linutronix.de \
    --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