From: Paolo Bonzini <pbonzini@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Borislav Petkov" <bp@suse.de>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Gary Hook" <gary.hook@amd.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Joerg Roedel" <joro@8bytes.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: SVM: kbuild test robot warning fixes
Date: Sat, 24 Feb 2018 01:16:43 +0100 [thread overview]
Message-ID: <b4aca2e0-a931-75cd-abaf-95bf72ec35ca@redhat.com> (raw)
In-Reply-To: <20180115133205.93859-1-brijesh.singh@amd.com>
On 15/01/2018 14:32, Brijesh Singh wrote:
> The patch series fixes the warnings reported by kbuild test robot
> after SEV patches. Additionally, during testing I found that LAUNCH_SECRET
> command was broken and patch series contains the fix for it.
>
> The patch series applies on kvm/queue branch.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: "Radim Krčmář" <rkrcmar@redhat.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Gary Hook <gary.hook@amd.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: linux-crypto@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> Brijesh Singh (4):
> crypto: ccp: Fix sparse, use plain integer as NULL pointer
> KVM: SVM: Fix sparse: incorrect type in argument 1 (different base
> types)
> include: psp-sev: Capitalize invalid length enum
> KVM: SVM: Fix SEV LAUNCH_SECRET command
>
> arch/x86/kvm/svm.c | 14 ++++++++++----
> drivers/crypto/ccp/psp-dev.c | 8 ++++----
> include/uapi/linux/psp-sev.h | 2 +-
> 3 files changed, 15 insertions(+), 9 deletions(-)
>
Applying patches 1 and 3 from this series, thanks.
Paolo
prev parent reply other threads:[~2018-02-24 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 13:32 Brijesh Singh
2018-01-15 13:32 ` [PATCH 1/4] crypto: ccp: Fix sparse, use plain integer as NULL pointer Brijesh Singh
2018-01-15 13:32 ` [PATCH 2/4] KVM: SVM: Fix sparse: incorrect type in argument 1 (different base types) Brijesh Singh
2018-01-15 13:32 ` [PATCH 3/4] include: psp-sev: Capitalize invalid length enum Brijesh Singh
2018-01-15 13:32 ` [PATCH 4/4] KVM: SVM: Fix SEV LAUNCH_SECRET command Brijesh Singh
2018-02-24 0:16 ` Paolo Bonzini [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=b4aca2e0-a931-75cd-abaf-95bf72ec35ca@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@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
all inboxes | Powered by JetHome®