From: Brijesh Singh <brijesh.singh@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: brijesh.singh@amd.com, x86@kernel.org, tglx@linutronix.de,
jroedel@suse.de, thomas.lendacky@amd.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com
Subject: Re: [PATCH 1/3] x86/sev-es: Rename sev-es.{ch} to sev.{ch}
Date: Wed, 28 Apr 2021 16:29:01 -0500 [thread overview]
Message-ID: <da102340-eaee-c76b-9773-bc63cf0e8f11@amd.com> (raw)
In-Reply-To: <YIhCwtMA6WnDNvxt@zn.tnic>
On 4/27/21 11:58 AM, Borislav Petkov wrote:
> On Tue, Apr 27, 2021 at 06:16:34AM -0500, Brijesh Singh wrote:
>> The SEV-SNP builds upon the SEV-ES functionality while adding new hardware
>> protection. Version 2 of the GHCB specification adds new NAE events that
>> are SEV-SNP specific. Rename the sev-es.{ch} to sev.{ch} so that we can
>> consolidate all the SEV-ES and SEV-SNP in a one place.
> No "we":
>
> ... so that all SEV* functionality can be consolidated in one place."
oops, I did it again :(.
Let know if you want me to send the updated description ?
>
> Rest looks good.
>
next prev parent reply other threads:[~2021-04-28 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 11:16 [PATCH 0/3] x86/sev-es: rename file and other cleanup Brijesh Singh
2021-04-27 11:16 ` [PATCH 1/3] x86/sev-es: Rename sev-es.{ch} to sev.{ch} Brijesh Singh
2021-04-27 16:58 ` Borislav Petkov
2021-04-28 21:29 ` Brijesh Singh [this message]
2021-05-10 8:43 ` [tip: x86/urgent] " tip-bot2 for Brijesh Singh
2021-04-27 11:16 ` [PATCH 2/3] x86/sev: Move GHCB MSR protocol and NAE definitions in a common header Brijesh Singh
2021-05-10 8:43 ` [tip: x86/urgent] " tip-bot2 for Brijesh Singh
2021-04-27 11:16 ` [PATCH 3/3] x86/msr: Rename MSR_K8_SYSCFG to MSR_AMD64_SYSCFG Brijesh Singh
2021-04-28 10:44 ` Borislav Petkov
2021-04-28 10:55 ` Paolo Bonzini
2021-04-28 11:27 ` Borislav Petkov
2021-04-28 11:30 ` Paolo Bonzini
2021-04-28 11:33 ` Borislav Petkov
2021-05-10 8:43 ` [tip: x86/urgent] " tip-bot2 for Brijesh Singh
2021-05-05 12:23 ` [PATCH 0/3] x86/sev-es: rename file and other cleanup Joerg Roedel
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=da102340-eaee-c76b-9773-bc63cf0e8f11@amd.com \
--to=brijesh.singh@amd.com \
--cc=bp@alien8.de \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).