[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <09FA3C31-BFC5-41FA-AB17-87E45EE2FB9B@zytor.com>
Date: Thu, 14 Mar 2019 19:21:07 -0700
From: hpa@...or.com
To: Konrad Rzeszutek Wilk <konrad@...nel.org>
CC: LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
X86 <x86@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
corbet@....net, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
kanth.ghatraju@...cle.com, Daniel Kiper <daniel.kiper@...cle.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
dpsmith@...rtussolutions.com,
Ross John Philipson <ross.philipson@...cle.com>
Subject: Re: [PATCH 1/1] x86: Secure Launch boot protocol
On March 14, 2019 11:53:18 AM PDT, Konrad Rzeszutek Wilk <konrad@...nel.org> wrote:
>.. snip..
>>
>> Double NAK – I'm in a meeting right now but with clarify shortly.
>
>Would it help if we had a meeting to brainstorm an acceptable solution?
>Thank you.
It would. I'll write up the immediate issues (which are trivial – just some misunderstanding of the boot protocol. I just wanted to make sure it didn't get merged and possibly get set in stone) later tonight, but it would be great to talk about underlying issues.
Do I remember right that you are on the east coast, or am I full of it.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists