All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	linux-spdx@vger.kernel.org
Subject: Re: [PATCH] lib/crc32: add SPDX license identifier
Date: Wed, 14 May 2025 09:39:33 +0200	[thread overview]
Message-ID: <2025051423-gallstone-carpentry-1c5a@gregkh> (raw)
In-Reply-To: <20250514061425.GA237199@sol>

On Tue, May 13, 2025 at 11:14:25PM -0700, Eric Biggers wrote:
> On Wed, May 14, 2025 at 08:11:40AM +0200, Thomas Gleixner wrote:
> > On Tue, May 13 2025 at 22:24, Eric Biggers wrote:
> > 
> > > From: Eric Biggers <ebiggers@google.com>
> > >
> > > lib/crc32.c and include/linux/crc32.h got missed by the bulk SPDX
> > > conversion because of the nonstandard explanation of the license.
> > > However, crc32.c clearly states that it's licensed under the GNU General
> > > Public License, Version 2.  And the comment in crc32.h clearly indicates
> > > that it's meant to have the same license as crc32.c.  Therefore, apply
> > > SPDX-License-Identifier: GPL-2.0-only to both files.
> > >
> > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > 
> > Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> 
> Thanks.
> 
> I forgot to mention: I'm planning to take this patch through the crc tree.

Great!

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

      reply	other threads:[~2025-05-14  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14  5:24 [PATCH] lib/crc32: add SPDX license identifier Eric Biggers
2025-05-14  6:11 ` Thomas Gleixner
2025-05-14  6:14   ` Eric Biggers
2025-05-14  7:39     ` Greg KH [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=2025051423-gallstone-carpentry-1c5a@gregkh \
    --to=greg@kroah.com \
    --cc=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.