public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: [GIT PULL] SPDX updates for 7.1-rc1
Date: Fri, 24 Apr 2026 15:18:49 +0200	[thread overview]
Message-ID: <aettudEFKIftgNrP@kroah.com> (raw)

The following changes since commit f338e77383789c0cae23ca3d48adcc5e9e137e3c:

  Linux 7.0-rc4 (2026-03-15 13:52:05 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git tags/spdx-7.1-rc1

for you to fetch changes up to ebf1bafd090790704ba54c032de299fccd90a9da:

  LICENSES: Explicitly allow SPDX-FileCopyrightText (2026-03-20 11:42:50 +0100)

----------------------------------------------------------------
SPDX change for 7.1-rc1

Here is a single SPDX-like change for 7.1-rc1.  It explicitly allows the
use of SPDX-FileCopyrightText which has been used already in many files.
At the same time, update checkpatch to catch any "non allowed" spdx
identifiers as we don't want to go overboard here.

This has been in linux-next for a long time with no reported problems.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Krzysztof Kozlowski (1):
      LICENSES: Explicitly allow SPDX-FileCopyrightText

 Documentation/process/license-rules.rst | 7 +++++--
 scripts/checkpatch.pl                   | 8 ++++++++
 2 files changed, 13 insertions(+), 2 deletions(-)

             reply	other threads:[~2026-04-24 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 13:18 Greg KH [this message]
2026-04-24 20:37 ` [GIT PULL] SPDX updates for 7.1-rc1 pr-tracker-bot

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=aettudEFKIftgNrP@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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