From: Segher Boessenkool <segher@kernel.crashing.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v3] powerpc: Add missing SPDX license identifiers
Date: Fri, 21 Jan 2022 12:15:44 -0600 [thread overview]
Message-ID: <20220121181544.GH614@gate.crashing.org> (raw)
In-Reply-To: <YerO8MjbXlvbMEsZ@kroah.com>
On Fri, Jan 21, 2022 at 04:19:12PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Jan 21, 2022 at 03:13:50PM +0000, Christophe Leroy wrote:
> > >> - * This file is free software; you can redistribute it and/or modify it
> > >> - * under the terms of the GNU General Public License as published by the
> > >> - * Free Software Foundation; either version 2, or (at your option) any
> > >> - * later version.
[ ... ]
> > >> * 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.
The "as a special exception" refers to "This file is free software;
you can redistribute it and/or modify it". It is meaningless without
having anything it is an exception *to* :-)
In general, you should never edit licence texts.
> > > Look at that "special exception", why are you ignoring it here? You
> > > can't do that :(
> >
> > I'm not ignoring it, that's the reason why I left it.
>
> You ignore that part of the license in the SPDX line, why?
>
> > Isn't it the correct way to do ? How should it be done ?
>
> You need to properly describe this in the SPDX line. You did not do so
> here, which means that any tool just looking at the SPDX line would get
> this license wrong.
A new label needs to be defined and documented. Should be pretty
mechanical to do, but that should see a wider audience than the powerpc
hackers :-)
Segher
next prev parent reply other threads:[~2022-01-21 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 11:03 [PATCH v3] powerpc: Add missing SPDX license identifiers Christophe Leroy
2022-01-21 14:35 ` Greg Kroah-Hartman
2022-01-21 15:13 ` Christophe Leroy
2022-01-21 15:19 ` Greg Kroah-Hartman
2022-01-21 15:34 ` Christophe Leroy
2022-01-21 16:00 ` Greg Kroah-Hartman
2022-01-21 18:15 ` Segher Boessenkool [this message]
2022-01-25 13:47 ` Bradley M. Kuhn
2022-01-21 14:36 ` Greg Kroah-Hartman
2022-01-21 18:09 ` Richard Fontana
2022-01-21 18:17 ` Richard Fontana
2022-01-22 5:20 ` J Lovejoy
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=20220121181544.GH614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox