From: hpa@zytor.com
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, X86 <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
corbet@lwn.net, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
kanth.ghatraju@oracle.com, Daniel Kiper <daniel.kiper@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
dpsmith@apertussolutions.com,
Ross John Philipson <ross.philipson@oracle.com>
Subject: Re: [PATCH 1/1] x86: Secure Launch boot protocol
Date: Thu, 14 Mar 2019 19:21:07 -0700 [thread overview]
Message-ID: <09FA3C31-BFC5-41FA-AB17-87E45EE2FB9B@zytor.com> (raw)
In-Reply-To: <CACJDEmpKxL=c-1zeBYR6v4JK=QN3vxd967HwBFHhTWmxPQhM4A@mail.gmail.com>
On March 14, 2019 11:53:18 AM PDT, Konrad Rzeszutek Wilk <konrad@kernel.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.
next prev parent reply other threads:[~2019-03-15 2:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 15:04 [PATCH 0/1] [RFC] " Ross Philipson
2019-03-11 15:04 ` [PATCH 1/1] x86: " Ross Philipson
2019-03-12 17:34 ` hpa
2019-03-14 18:53 ` Konrad Rzeszutek Wilk
2019-03-15 2:21 ` hpa [this message]
2019-03-28 18:15 ` [PATCH 0/1] [RFC] " H. Peter Anvin
2019-03-28 18:37 ` Daniel Kiper
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=09FA3C31-BFC5-41FA-AB17-87E45EE2FB9B@zytor.com \
--to=hpa@zytor.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.kiper@oracle.com \
--cc=dpsmith@apertussolutions.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ross.philipson@oracle.com \
--cc=tglx@linutronix.de \
--cc=x86@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®