linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-spdx@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] LICENSES: add CC0-1.0 license text
Date: Wed, 21 May 2025 14:54:30 +0200	[thread overview]
Message-ID: <2025052118-handbook-dowry-bae9@gregkh> (raw)
In-Reply-To: <20250513115912.303082-1-lukas.bulwahn@redhat.com>

On Tue, May 13, 2025 at 01:59:12PM +0200, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> 
> Commit cbbd847d107f ("tools/x86/kcpuid: Introduce a complete cpuid
> bitfields CSV file") turns the tools/arch/x86/kcpuid/cpuid.csv to be an
> auto-generated file from an input file maintained at x86-cpuid.org project.
> The x86-cpuid.org project clearly states that the auto-generated file is to
> be licensed with CC0-1.0 (see Link below). So, the SPDX-License-Identifier
> CC0-1.0 in the file is correct as intended.
> 
> The spdxcheck.py script reports that tools/arch/x86/kcpuid/cpuid.csv uses
> an Invalid License ID: CC0-1.0, though, as the LICENSES directory in the
> kernel tree does not contain a file with license information for CC0-1.0.
> 
> Add a suitable CC0-1.0 file with the license text into LICENSES/deprecated
> to make spdxcheck.py happy.
> 
> The directory deprecated is the best fit, by exclusion of the
> alternatives. CC0-1.0 should not be considered among the preferred licenses
> in the kernel, nor is it a license exception case or intended for
> dual-licensing some copyrighted material. So, deprecated is the best fit
> here, even if the license and its use is fine and it does not suggest to
> actually deprecate use of this license.
> 
> The license text for the CC0-1.0 file was obtained from the spdx
> license-list-data git repository (see Link below).
> 
> Link: https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/blob/v2.4/LICENSE.rst
> Link: https://github.com/spdx/license-list-data/blob/main/text/CC0-1.0.txt
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> ---
>  LICENSES/deprecated/CC0-1.0 | 129 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 129 insertions(+)

Thanks for this, I'll add it to the spdx tree now.

greg k-h

      reply	other threads:[~2025-05-21 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 11:59 [PATCH] LICENSES: add CC0-1.0 license text Lukas Bulwahn
2025-05-21 12:54 ` Greg Kroah-Hartman [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=2025052118-handbook-dowry-bae9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --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).