From: Gary R Hook <ghook@amd.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Gary R Hook <gary.hook@amd.com>
Cc: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Brijesh Singh <brijesh.singh@amd.com>,
Borislav Petkov <bp@suse.de>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCHv2 0/2] Add new SEV commands
Date: Thu, 31 May 2018 07:43:13 -0500 [thread overview]
Message-ID: <8210dfee-3370-743a-6e9e-96df0ceadf11@amd.com> (raw)
In-Reply-To: <20180531064534.ldi2ysuhh2omex5d@gondor.apana.org.au>
On 05/31/2018 01:45 AM, Herbert Xu wrote:
> On Wed, May 30, 2018 at 01:44:12PM -0500, Gary R Hook wrote:
>> On 05/30/2018 11:28 AM, Herbert Xu wrote:
>>> On Fri, May 25, 2018 at 03:23:28PM -0500, Janakarajan Natarajan wrote:
>>>> This patchset adds two new SEV commands, introduced in SEV API v0.15
>>>> and v0.16 respectively.
>>>>
>>>> * DOWNLOAD_FIRMWARE allows the SEV firmware to be updated if a blob newer
>>>> than or similar to the exisiting build is available.
>>>>
>>>> * GET_ID allows to query for a unique ID that can be used to retrieve the
>>>> Chip Endorsment Key (CEK) public key signed by the AMD SEV Signing Key
>>>> (ASK).
>>>>
>>>> v1->v2:
>>>> * Added cover letter.
>>>> * Misc changes based on Boris' feedback.
>>>>
>>>> Janakarajan Natarajan (2):
>>>> crypto: ccp: Add DOWNLOAD_FIRMWARE SEV command
>>>> crypto: ccp: Add GET_ID SEV command
>>>>
>>>> drivers/crypto/ccp/psp-dev.c | 143 ++++++++++++++++++++++++++++++++++++++++---
>>>> drivers/crypto/ccp/psp-dev.h | 4 ++
>>>> include/linux/psp-sev.h | 23 +++++++
>>>> include/uapi/linux/psp-sev.h | 12 ++++
>>>> 4 files changed, 172 insertions(+), 10 deletions(-)
>>>
>>> All applied. Thanks.
>>
>> Huh. Without a Reviewed-by or an Acked-by?
>
> These patches have been out there for weeks. If you were going
> to object you should have done so by now.
Oh, yes, agreed. This was a question about protocol, not the patches
themselves. But if you're happy, I'm happy.
Thanks.
prev parent reply other threads:[~2018-05-31 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 20:23 [PATCHv2 0/2] Add new SEV commands Janakarajan Natarajan
2018-05-25 20:23 ` [PATCHv2 1/2] crypto: ccp: Add DOWNLOAD_FIRMWARE SEV command Janakarajan Natarajan
2018-05-25 20:23 ` [PATCHv2 2/2] crypto: ccp: Add GET_ID " Janakarajan Natarajan
2018-05-29 18:46 ` [PATCHv2 0/2] Add new SEV commands Paolo Bonzini
2018-05-29 18:47 ` Gary R Hook
2018-05-30 13:43 ` Brijesh Singh
2018-05-30 16:28 ` Herbert Xu
2018-05-30 18:44 ` Gary R Hook
2018-05-31 6:45 ` Herbert Xu
2018-05-31 12:43 ` Gary R Hook [this message]
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=8210dfee-3370-743a-6e9e-96df0ceadf11@amd.com \
--to=ghook@amd.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.com \
/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