From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Marc-Etienne Vargenau (Nokia)" <marc-etienne.vargenau@nokia.com>
Cc: Thomas Huth <thuth@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>
Subject: Re: [PATCH] arch/x86/kvm/ioapic: Remove license boilerplate with bad FSF address
Date: Mon, 28 Jul 2025 17:07:20 +0200 [thread overview]
Message-ID: <2025072843-browbeat-rocket-c549@gregkh> (raw)
In-Reply-To: <PR3PR07MB81837F4778329A2270CC9318AC5AA@PR3PR07MB8183.eurprd07.prod.outlook.com>
On Mon, Jul 28, 2025 at 02:59:26PM +0000, Marc-Etienne Vargenau (Nokia) wrote:
> Hello,
>
> That should be:
> // SPDX-License-Identifier: LGPL-2.1-or-later
> not
> // SPDX-License-Identifier: LGPL-2.1+
>
> « LGPL-2.1+ » is deprecated
> https://spdx.org/licenses/LGPL-2.1+.html
The kernel does not differenciate between the two at this point in time,
sorry. Either is fine for now.
Only AFTER we actually tag all files in the tree will we worry about
silly things like this.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-28 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 14:15 [PATCH] arch/x86/kvm/ioapic: Remove license boilerplate with bad FSF address Thomas Huth
[not found] ` <PR3PR07MB81837F4778329A2270CC9318AC5AA@PR3PR07MB8183.eurprd07.prod.outlook.com>
2025-07-28 15:01 ` Thomas Huth
2025-07-28 15:07 ` Greg Kroah-Hartman [this message]
[not found] ` <PR3PR07MB81835DAC6ACE7162E81A3AC4AC5AA@PR3PR07MB8183.eurprd07.prod.outlook.com>
2025-07-28 15:34 ` Greg Kroah-Hartman
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=2025072843-browbeat-rocket-c549@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=marc-etienne.vargenau@nokia.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=x86@kernel.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