From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Thomas Huth <thuth@redhat.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Thomas Gleixner <tglx@linutronix.de>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: Re: [PATCH v2] powerpc: Replace the obsolete address of the FSF
Date: Fri, 11 Jul 2025 09:38:43 +0200 [thread overview]
Message-ID: <2025071119-important-convene-ab85@gregkh> (raw)
In-Reply-To: <aHC-Ke2oLri_m7p6@infradead.org>
On Fri, Jul 11, 2025 at 12:32:57AM -0700, Christoph Hellwig wrote:
> On Fri, Jul 11, 2025 at 09:30:31AM +0200, Greg Kroah-Hartman wrote:
> > That's a crazy exception, and one that should probably be talked about
> > with the FSF to determine exactly what the SPDX lines should be.
>
> It is called the libgcc exception and has been around forever for the
> files in libgcc.a that a lot of these low-level kernel helpers were
> copied from as the kernel doesn't link libgcc.
Ah, so it would be something like this exception:
https://spdx.org/licenses/GCC-exception-2.0.html
but the wording doesn't seem to match.
I'll let the license lawyers figure this out, thanks for the hint!
greg k-h
next prev parent reply other threads:[~2025-07-11 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 5:35 [PATCH v2] powerpc: Replace the obsolete address of the FSF Thomas Huth
2025-07-11 5:52 ` Greg Kroah-Hartman
2025-07-11 7:09 ` Thomas Huth
2025-07-11 7:30 ` Greg Kroah-Hartman
2025-07-11 7:32 ` Christoph Hellwig
2025-07-11 7:38 ` Greg Kroah-Hartman [this message]
2025-07-11 21:02 ` Richard Fontana
2025-07-11 23:13 ` Segher Boessenkool
2025-07-11 23:25 ` Richard Fontana
2025-07-12 22:48 ` Maciej W. Rozycki
2025-07-13 13:27 ` Richard Fontana
2025-07-17 13:06 ` Zavras, Alexios
2025-07-25 8:44 ` Zavras, Alexios
2025-07-13 14:01 ` Segher Boessenkool
2025-07-11 23:19 ` Segher Boessenkool
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=2025071119-important-convene-ab85@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
/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.