From: Segher Boessenkool <segher@kernel.crashing.org>
To: Richard Fontana <rfontana@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@infradead.org>,
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,
J Lovejoy <opensource@jilayne.com>
Subject: Re: [PATCH v2] powerpc: Replace the obsolete address of the FSF
Date: Fri, 11 Jul 2025 18:13:01 -0500 [thread overview]
Message-ID: <aHGafTZTcdlpw1gN@gate> (raw)
In-Reply-To: <CAC1cPGx0Chmz3s+rd5AJAPNCuoyZX-AGC=hfp9JPAG_-H_J6vw@mail.gmail.com>
On Fri, Jul 11, 2025 at 05:02:18PM -0400, Richard Fontana wrote:
> On Fri, Jul 11, 2025 at 3:38 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > 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!
>
> This one
>
> * In addition to the permissions in the GNU General Public License, the
> * Free Software Foundation gives you unlimited permission to link the
> * compiled version of this file with other programs, and to distribute
> * those programs without any restriction coming from the use of this
> * file. (The General Public License restrictions do apply in other
> * respects; for example, they cover modification of the file, and
> * distribution when not linked into another program.)
>
> is `GCC-exception-2.0`
>
> while this one:
>
> * As a special exception, if you link this library with files
> * compiled with GCC to produce an executable, this does not cause
> * the resulting executable to be covered by the GNU General Public License.
> * This exception does not however invalidate any other reasons why
> * the executable file might be covered by the GNU General Public License.
>
> does not seem to be in the SPDX exception list. It is very similar to
> `GNU-compiler-exception` except it specifically mentions GCC instead
> of saying "a GNU compiler".
https://spdx.org/licenses/GNU-compiler-exception.html
is exactly this.
Segher
next prev parent reply other threads:[~2025-07-11 23:14 UTC|newest]
Thread overview: 14+ 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
2025-07-11 21:02 ` Richard Fontana
2025-07-11 23:13 ` Segher Boessenkool [this message]
2025-07-11 23:25 ` Richard Fontana
2025-07-12 22:48 ` Maciej W. Rozycki
2025-07-13 13:27 ` Richard Fontana
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=aHGafTZTcdlpw1gN@gate \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--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=opensource@jilayne.com \
--cc=rfontana@redhat.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 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).