From: Jo Van Bulck <jo.vanbulck@cs.kuleuven.be>
To: Jarkko Sakkinen <jarkko@kernel.org>,
linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com
Subject: Re: [PATCH 0/4] selftests/sgx: Harden test enclave
Date: Mon, 7 Aug 2023 08:06:03 +0200 [thread overview]
Message-ID: <d3ad2bfb-2d64-73f5-7e37-0119eaa89c93@cs.kuleuven.be> (raw)
In-Reply-To: <CUE17WOKP8HH.39KZQV0H8IRBV@seitikki>
On 28.07.23 20:54, Jarkko Sakkinen wrote
> It should be relatively easy to relicense the code as most of the
> commits have Intel copyright.
>
> Personally I would not mind because that would give opportunity for
> code that I wrote to have a wider audience but it needs to be forked
> with some other license first.
> I support also the idea of refining the selftest as a run-time, which
> could perhaps consist of the following steps:
>
> 1. Create a repository of the self-compiling selftest with GPLv2. You
> could add also AUTHORS file for the initial content by crawling this
> data from the git log.
> 2. Create a commit with sob's from the required stakeholders, which
> changes the license to something more appropriate, and get the
> sob's with some process.
Thank you Jarkko, appreciated! I plan to start working on the fork from
next month onwards. However, I think GPL would be the best license for
this project and I'd prefer to stick to it for the time being.
Best,
Jo
next prev parent reply other threads:[~2023-08-07 6:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 14:24 [PATCH 0/4] selftests/sgx: Harden test enclave Jo Van Bulck
2023-07-19 14:24 ` [PATCH 1/4] selftests/sgx: Harden test enclave ABI Jo Van Bulck
2023-07-20 17:27 ` Jarkko Sakkinen
2023-07-20 19:14 ` Jo Van Bulck
2023-07-19 14:24 ` [PATCH 2/4] selftests/sgx: Store base address and size in test enclave Jo Van Bulck
2023-07-20 17:29 ` Jarkko Sakkinen
2023-07-20 19:18 ` Jo Van Bulck
2023-07-19 14:24 ` [PATCH 3/4] selftests/sgx: Harden test enclave API Jo Van Bulck
2023-07-20 17:32 ` Jarkko Sakkinen
2023-07-20 19:34 ` Jo Van Bulck
2023-07-19 14:25 ` [PATCH 4/4] selftests/sgx: Fix compiler optimizations in test enclave Jo Van Bulck
2023-07-20 17:25 ` [PATCH 0/4] selftests/sgx: Harden " Jarkko Sakkinen
2023-07-20 19:12 ` Jo Van Bulck
2023-07-20 19:56 ` Dave Hansen
2023-07-20 20:57 ` Jo Van Bulck
2023-07-22 18:10 ` Jarkko Sakkinen
2023-07-24 10:46 ` Jo Van Bulck
2023-07-28 18:54 ` Jarkko Sakkinen
2023-08-07 6:06 ` Jo Van Bulck [this message]
2023-08-07 11:58 ` Jarkko Sakkinen
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=d3ad2bfb-2d64-73f5-7e37-0119eaa89c93@cs.kuleuven.be \
--to=jo.vanbulck@cs.kuleuven.be \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@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