linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: tglx@linutronix.de, gregkh@linuxfoundation.org,
	akpm@linux-foundation.org, shuah@kernel.org,
	keescook@chromium.org
Cc: joe@perches.com, mcgrof@kernel.org, rostedt@goodmis.org,
	linux-spdx@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v11 0/2] SPDX: add copyleft-next-0.3.1
Date: Mon,  3 Oct 2022 09:58:47 -0700	[thread overview]
Message-ID: <20221003165849.1658170-1-mcgrof@kernel.org> (raw)

As suggested by Thomas Gleixner, I'm following up to move on with
the SPDX tag needed for copyleft-next-0.3.1. I've split this out
from the test_sysfs selftest so to separate review from that.

Changes on this v11:
  o Fixed a minor typo on patch #2 as noted by Kees Cook
  o Added Reviewed-by tags by Kees Cook

Changes on this v10:
  o embraced paragraph from Thomas Gleixner which helps explain why             
    the OR operator in the SPDX license name
  o dropped the GPL-2.0 and GPL-2.0+ tags as suggested by Thomas Gleixner
    as these are outdated (still valid) in the SPDX spec
  o trimmed the Cc list to remove the test_sysfs / block layer / fs folks as
    the test_sysfs stuff is now dropped from consideration in this series

Prior to this the series was at v9 but it also had the test_sysfs and its
changes, its history can be found here:

https://lore.kernel.org/all/20211029184500.2821444-1-mcgrof@kernel.org/

Luis Chamberlain (2):
  LICENSES: Add the copyleft-next-0.3.1 license
  testing: use the copyleft-next-0.3.1 SPDX tag

 LICENSES/dual/copyleft-next-0.3.1        | 236 +++++++++++++++++++++++
 lib/test_kmod.c                          |  12 +-
 lib/test_sysctl.c                        |  12 +-
 tools/testing/selftests/kmod/kmod.sh     |  13 +-
 tools/testing/selftests/sysctl/sysctl.sh |  12 +-
 5 files changed, 240 insertions(+), 45 deletions(-)
 create mode 100644 LICENSES/dual/copyleft-next-0.3.1

-- 
2.35.1


             reply	other threads:[~2022-10-03 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 16:58 Luis Chamberlain [this message]
2022-10-03 16:58 ` [PATCH v11 1/2] LICENSES: Add the copyleft-next-0.3.1 license Luis Chamberlain
2022-10-03 18:47   ` Bird, Tim
2022-10-03 16:58 ` [PATCH v11 2/2] testing: use the copyleft-next-0.3.1 SPDX tag Luis Chamberlain
2022-10-03 18:42   ` Bird, Tim
2022-10-19 13:26 ` [PATCH v11 0/2] SPDX: add copyleft-next-0.3.1 Luis Chamberlain
2022-10-19 15:00   ` Greg KH

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=20221003165849.1658170-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).