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 update for 5.19-rc1
Date: Fri, 3 Jun 2022 12:21:51 +0200 [thread overview]
Message-ID: <Ypngv8MIQ/Syj1Js@kroah.com> (raw)
The following changes since commit 42226c989789d8da4af1de0c31070c96726d990c:
Linux 5.18-rc7 (2022-05-15 18:08:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git tags/spdx-5.19-rc1
for you to fetch changes up to 53c83d6d8e399fad3d3d25df0ea0d54eb0f94f88:
siphash: add SPDX tags as sole licensing authority (2022-05-19 18:54:22 +0200)
----------------------------------------------------------------
SPDX changes for 5.19-rc1
Here are some SPDX (i.e. licensing) changes for 5.19-rc1
The SPDX-labeling effort has started to pick up again, so here are some
changes for various parts of the tree that are related to this effort.
Included in here are:
- freevxfs license updates
- spihash.c license cleanups
- spdxcheck script updates to make things easier to work with
going forward
All of the license updates came from the original authors/copyright
holders of the code involved.
All of these have been in linux-next for weeks with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Christoph Hellwig (1):
freevxfs: relicense to GPLv2 only
Jason A. Donenfeld (1):
siphash: add SPDX tags as sole licensing authority
Thomas Gleixner (8):
scripts/spdxcheck: Add percentage to statistics
scripts/spdxcheck: Add directory statistics
scripts/spdxcheck: Add [sub]directory statistics
scripts/spdxcheck: Add option to display files without SPDX
scripts/spdxcheck: Put excluded files and directories into a separate file
scripts/spdxcheck: Exclude config directories
scripts/spdxcheck: Exclude MAINTAINERS/CREDITS
scripts/spdxcheck: Exclude top-level README
fs/freevxfs/vxfs.h | 27 +------
fs/freevxfs/vxfs_bmap.c | 26 +------
fs/freevxfs/vxfs_dir.h | 27 +------
fs/freevxfs/vxfs_extern.h | 27 +------
fs/freevxfs/vxfs_fshead.c | 26 +------
fs/freevxfs/vxfs_fshead.h | 27 +------
fs/freevxfs/vxfs_immed.c | 26 +------
fs/freevxfs/vxfs_inode.c | 26 +------
fs/freevxfs/vxfs_inode.h | 27 +------
fs/freevxfs/vxfs_lookup.c | 26 +------
fs/freevxfs/vxfs_olt.c | 26 +------
fs/freevxfs/vxfs_olt.h | 27 +------
fs/freevxfs/vxfs_subr.c | 26 +------
fs/freevxfs/vxfs_super.c | 26 +------
include/linux/siphash.h | 5 +-
lib/siphash.c | 5 +-
lib/test_siphash.c | 7 +-
scripts/spdxcheck.py | 175 ++++++++++++++++++++++++++++++++++++++++++----
scripts/spdxexclude | 18 +++++
19 files changed, 202 insertions(+), 378 deletions(-)
create mode 100644 scripts/spdxexclude
next reply other threads:[~2022-06-03 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 10:21 Greg KH [this message]
2022-06-03 18:50 ` [GIT PULL] SPDX update for 5.19-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=Ypngv8MIQ/Syj1Js@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