[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a225d74-0f57-fedd-da31-c11c4f57961d@intel.com>
Date: Fri, 19 Apr 2019 07:25:49 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "Dr. Greg" <greg@...ellic.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
x86@...nel.org, linux-sgx@...r.kernel.org,
akpm@...ux-foundation.org, sean.j.christopherson@...el.com,
nhorman@...hat.com, npmccallum@...hat.com, serge.ayoun@...el.com,
shay.katz-zamir@...el.com, haitao.huang@...el.com,
andriy.shevchenko@...ux.intel.com, tglx@...utronix.de,
kai.svahn@...el.com, bp@...en8.de, josh@...htriplett.org,
luto@...nel.org, kai.huang@...el.com, rientjes@...gle.com
Subject: Re: [PATCH v20 00/28] Intel SGX1 support
On 4/19/19 7:17 AM, Dr. Greg wrote:
> 3.) The approach we propose addresses these issues while imposing no
> functional limitations on how Linux platform owners can use enclave
> technology.
Let's say v20 gets merged. Is there any reason your approach can not be
rebased on top of that code, reviewed and merged later?
Powered by blists - more mailing lists