From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] m68k/powerpc: Kill references to non-existent README.legal
Date: Thu, 7 Sep 2023 14:25:29 +0000 [thread overview]
Message-ID: <5c80dc63-e7d0-5d82-de83-7e35c54b8351@csgroup.eu> (raw)
In-Reply-To: <cover.1694095086.git.geert@linux-m68k.org>
Le 07/09/2023 à 16:21, Geert Uytterhoeven a écrit :
> Hi all,
>
> Several source files contain license boilerplate that refers to the file
> "README.legal", which never existed in upstream Linux. This is a relic
> from the early port of Linux to the m68k processor family, before it was
> merged in v1.3.94. Later, copies of this boilerplate ended up in the
> PowerPC port.
>
> The "README.legal" file (from e.g. [1]) read:
>
> ---8<-----------------------------------------------------------------
> Legal information about the Linux/68k software package
>
> All files contained in this archive are copyrighted by one or more
> person. They are not in the public domain.
>
> Most of the files are copyrighted by Linus Torvalds, the original
> writer of Linux for IBM PC clone systems. Some parts are copyrighted
> by other IBM PC linux developers. Other parts are copyrighted by
> Linux/68k developers.
>
> This package is subject to the terms and conditions of the GNU General
> Public License. A copy of this license may be found in the file named
> "COPYING" which should be in the same directory as this file. If the
> file has been omitted, you may obtain it by writing to the Free
> Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> ----------------------------------------------------------------->8---
>
> Note that the "COPYING" file at that time corresponded to the version
> from upstream Linux v0.99.11 until v2.1.104, and thus predated the
> addition of the "only valid GPL version is v2" clause in v2.4.0-test8.
>
> This patch series gets rid of the references to README.legal by
> replacing the boilerplate with SPDX license identifiers.
>
> Thanks for your comments!
As far as I know this kind of patch has to be copied to
linux-spdx@vger.kernel.org
Christophe
>
> [1] https://www.ibiblio.org/pub/historic-linux/ftp-archives/tsx-11.mit.edu/Oct-07-1996/680x0/v0.9/linux-0.9.tar.gz
>
> Geert Uytterhoeven (2):
> m68k: Replace GPL 2.0+ README.legal boilerplate by SPDX
> powerpc: Replace GPL 2.0+ README.legal boilerplate by SPDX
>
> arch/m68k/68000/entry.S | 7 ++-----
> arch/m68k/bvme6000/config.c | 5 +----
> arch/m68k/coldfire/entry.S | 7 ++-----
> arch/m68k/ifpsp060/Makefile | 6 ++----
> arch/m68k/kernel/entry.S | 7 ++-----
> arch/m68k/kernel/head.S | 8 ++------
> arch/m68k/mvme147/config.c | 5 +----
> arch/m68k/mvme16x/config.c | 5 +----
> arch/m68k/q40/config.c | 5 +----
> arch/powerpc/kernel/ptrace/ptrace.c | 5 +----
> arch/powerpc/kernel/signal.c | 5 +----
> arch/powerpc/kernel/signal.h | 7 ++-----
> 12 files changed, 18 insertions(+), 54 deletions(-)
>
next prev parent reply other threads:[~2023-09-07 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 14:21 [PATCH 0/2] m68k/powerpc: Kill references to non-existent README.legal Geert Uytterhoeven
2023-09-07 14:21 ` [PATCH 1/2] m68k: Replace GPL 2.0+ README.legal boilerplate by SPDX Geert Uytterhoeven
2023-09-08 2:09 ` Greg Ungerer
2023-09-07 14:21 ` [PATCH 2/2] powerpc: " Geert Uytterhoeven
2023-09-07 14:25 ` Christophe Leroy [this message]
2023-09-07 14:36 ` [PATCH 0/2] m68k/powerpc: Kill references to non-existent README.legal Geert Uytterhoeven
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=5c80dc63-e7d0-5d82-de83-7e35c54b8351@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).