From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: david@redhat.com, cohuck@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 2/2] s390x: lib: Move to GPL 2 and SPDX license identifiers
Date: Tue, 8 Dec 2020 16:21:39 +0100 [thread overview]
Message-ID: <4f5ae2c0-65ff-1c12-958d-d6478fe1383b@redhat.com> (raw)
In-Reply-To: <20201208150902.32383-3-frankja@linux.ibm.com>
On 08/12/2020 16.09, Janosch Frank wrote:
> In the past we had some issues when developers wanted to use code
> snippets or constants from the kernel in a test or in the library. To
> remedy that the s390x maintainers decided to move all files to GPL 2
> (if possible).
>
> At the same time let's move to SPDX identifiers as they are much nicer
> to read.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-12-08 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 15:09 [kvm-unit-tests PATCH 0/2] s390x: Move from LGPL 2 to GPL 2 Janosch Frank
2020-12-08 15:09 ` [kvm-unit-tests PATCH 1/2] s390x: Move to GPL 2 and SPDX license identifiers Janosch Frank
2020-12-08 15:14 ` Thomas Huth
2020-12-09 9:12 ` David Hildenbrand
2020-12-09 9:19 ` David Hildenbrand
2020-12-09 9:49 ` Janosch Frank
2020-12-09 11:01 ` Cornelia Huck
2020-12-09 12:43 ` Pierre Morel
2020-12-08 15:09 ` [kvm-unit-tests PATCH 2/2] s390x: lib: " Janosch Frank
2020-12-08 15:21 ` Thomas Huth [this message]
2020-12-09 9:15 ` David Hildenbrand
2020-12-09 9:46 ` Janosch Frank
2020-12-10 16:15 ` David Hildenbrand
2020-12-10 16:20 ` Janosch Frank
2020-12-09 11:03 ` Cornelia Huck
2020-12-09 12:50 ` Pierre Morel
2020-12-09 9:01 ` [kvm-unit-tests PATCH 0/2] s390x: Move from LGPL 2 to GPL 2 Christian Borntraeger
2020-12-09 10:16 ` Claudio Imbrenda
2020-12-09 16:07 ` Janosch Frank
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=4f5ae2c0-65ff-1c12-958d-d6478fe1383b@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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