mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Shuah Khan <shuah@kernel.org>,
	Michael Jeanson <mjeanson@efficios.com>,
	Peter Oskolkov <posk@posk.io>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Paul Burton <paulburton@kernel.org>,
	Sabyasachi Gupta <sabyasachi.linux@gmail.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Vincent Chen <vincent.chen@sifive.com>,
	Will Deacon <will@kernel.org>,
	Xingxing Su <suxingxing@loongson.cn>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Request for contributor approval: Relicensing rseq selftests to MIT
Date: Mon, 6 Feb 2023 13:36:19 -0500	[thread overview]
Message-ID: <da1bfb8a-5a88-5697-1c39-8e15c3c208a6@efficios.com> (raw)

Hi,

I would like to get contributor approval to relicense the rseq selftests 
within the Linux kernel and the librseq project to MIT. This will make 
it easier to use librseq from statically built applications, and I wish 
to continue sharing code between the kernel rseq selftests and librseq.

Allowing use of rseq application headers from statically built 
applications was the intent from the beginning, but it turns out that 
having the rseq.c initialization code under LGPL2.1 makes it harder than 
it should be for users.

The current contributor summary commit-wise under
tools/testing/selftests/rseq is:

    269  Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
      6  Michael Ellerman <mpe@ellerman.id.au>
      5  Shuah Khan <skhan@linuxfoundation.org>
      3  Michael Jeanson <mjeanson@efficios.com>
      3  Peter Oskolkov <posk@google.com>
      2  Martin Schwidefsky <schwidefsky@de.ibm.com>
      1  Masahiro Yamada <masahiroy@kernel.org>
      1  Paul Burton <paulburton@kernel.org>
      1  Sabyasachi Gupta <sabyasachi.linux@gmail.com>
      1  Vasily Gorbik <gor@linux.ibm.com>
      1  Vincent Chen <vincent.chen@sifive.com>
      1  Will Deacon <will@kernel.org>
      1  Xingxing Su <suxingxing@loongson.cn>

Header files are currently dual-licensed LGPL2.1/MIT, which is
somewhat redundant with plain MIT.

rseq.c was licensed under LGPL2.1. Relicencing it to MIT will facilitate 
its integration into statically built applications.

In order to facilitate eventual code sharing between tests and the
library implementation, I would like to relicense the tests from LGPL2.1 
to MIT as well.

Many of the contributions are trivial, but I prefer to kindly ask for 
approval nevertheless.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

             reply	other threads:[~2023-02-06 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 18:36 Mathieu Desnoyers [this message]
2023-02-06 18:45 ` Peter Oskolkov
2023-02-06 18:58 ` Mathieu Desnoyers
2023-02-06 19:17   ` Mathieu Desnoyers

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=da1bfb8a-5a88-5697-1c39-8e15c3c208a6@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mjeanson@efficios.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulburton@kernel.org \
    --cc=posk@posk.io \
    --cc=sabyasachi.linux@gmail.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=shuah@kernel.org \
    --cc=suxingxing@loongson.cn \
    --cc=vincent.chen@sifive.com \
    --cc=will@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

all inboxes | Powered by JetHome®