From: Michael Ellerman <mpe@ellerman.id.au>
To: Greg Ungerer <gerg@linux-m68k.org>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linuxppc-dev@lists.ozlabs.org,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 0/2] m68k/powerpc: Kill references to non-existent README.legal
Date: Sun, 15 Oct 2023 21:04:58 +1100 [thread overview]
Message-ID: <169736429851.960528.8922488798725928458.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1695031668.git.geert@linux-m68k.org>
On Mon, 18 Sep 2023 12:14:42 +0200, Geert Uytterhoeven wrote:
> 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.
>
> [...]
Applied to powerpc/next.
[2/2] powerpc: Replace GPL 2.0+ README.legal boilerplate with SPDX
https://git.kernel.org/powerpc/c/6fcb13972bc2b41211e1dddb02f5e73199addc75
cheers
prev parent reply other threads:[~2023-10-15 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 10:14 [PATCH v2 0/2] m68k/powerpc: Kill references to non-existent README.legal Geert Uytterhoeven
2023-09-18 10:14 ` [PATCH v2 1/2] m68k: Replace GPL 2.0+ README.legal boilerplate with SPDX Geert Uytterhoeven
2023-09-18 10:14 ` [PATCH v2 2/2] powerpc: " Geert Uytterhoeven
2023-09-19 2:12 ` Michael Ellerman
2023-09-19 6:43 ` Geert Uytterhoeven
2023-09-19 10:05 ` Michael Ellerman
2023-10-15 10:04 ` Michael Ellerman [this message]
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=169736429851.960528.8922488798725928458.b4-ty@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).