[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4bd7d47ef5478023dc27323fb2d6a7b2d7879787.camel@linux.intel.com>
Date: Thu, 14 May 2020 01:18:18 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Nathaniel McCallum <npmccallum@...hat.com>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
linux-sgx@...r.kernel.org, akpm@...ux-foundation.org,
dave.hansen@...el.com,
"Christopherson, Sean J" <sean.j.christopherson@...el.com>,
Neil Horman <nhorman@...hat.com>,
"Huang, Haitao" <haitao.huang@...el.com>,
andriy.shevchenko@...ux.intel.com, tglx@...utronix.de,
"Svahn, Kai" <kai.svahn@...el.com>, bp@...en8.de,
Josh Triplett <josh@...htriplett.org>, luto@...nel.org,
kai.huang@...el.com, David Rientjes <rientjes@...gle.com>,
"Xing, Cedric" <cedric.xing@...el.com>,
Patrick Uiterwijk <puiterwijk@...hat.com>
Subject: Re: [PATCH v29 00/20] Intel SGX foundations
On Thu, 2020-05-14 at 01:14 +0300, Jarkko Sakkinen wrote:
> On Wed, 2020-05-06 at 17:42 -0400, Nathaniel McCallum wrote:
> > Tested on Enarx. This requires a patch[0] for v29 support.
> >
> > Tested-by: Nathaniel McCallum <npmccallum@...hat.com>
>
> Thank you. Update in my tree.
>
> Sean, I'll fixed that whitespace issue too in my tree.
>
> General question: maybe it would be easiest that I issue a pull request
> once everyone feels that the series is ready to be pulled and stop sending
> new versions of the series?
My honest feelings about the series ATM are:
1. It is not perfect like no code never is and there are always issues.
2. Some things are very well matured, even more so than in a lot of mainline
code I've seen. I'm particularly happy how the locking code has been
converged.
3. Not worried to maintain the code in its current state. It is manageable.
/Jarkko
Powered by blists - more mailing lists