From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: x86: Fix kvm/queue breakage on clang
Date: Thu, 16 Mar 2023 13:07:31 +0100 [thread overview]
Message-ID: <b98945f0-09ef-158a-9348-e518469ec7e3@redhat.com> (raw)
In-Reply-To: <20230315191128.1407655-1-seanjc@google.com>
Am 15/03/2023 um 20:11 schrieb Sean Christopherson:
> Fix clang build errors for patches sitting kvm/queue. Ideally, these
> fixes will be squashed before the buggy commits make their way to kvm/next.
> If you do fixup kvm/queue, the VMX commit also has a bad SOB chain; Jim
> either needs to be listed as the author or his SOB needs to be deleted.
>
> Sean Christopherson (2):
> KVM: VMX: Drop unprotected-by-braces variable declaration in
> case-statement
> KVM: SVM: Drop unprotected-by-braces variable declaration in
> case-statement
>
> arch/x86/kvm/svm/svm.c | 5 ++---
> arch/x86/kvm/vmx/vmx.c | 4 +---
> 2 files changed, 3 insertions(+), 6 deletions(-)
>
>
> base-commit: 95b9779c1758f03cf494e8550d6249a40089ed1c
Note to self: compile patches also with clang, since gcc didn't complain
about missing brackets in a switch case.
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
next prev parent reply other threads:[~2023-03-16 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 19:11 [PATCH 0/2] KVM: x86: Fix kvm/queue breakage on clang Sean Christopherson
2023-03-15 19:11 ` [PATCH 1/2] KVM: VMX: Drop unprotected-by-braces variable declaration in case-statement Sean Christopherson
2023-03-15 19:11 ` [PATCH 2/2] KVM: SVM: " Sean Christopherson
2023-03-16 12:07 ` Emanuele Giuseppe Esposito [this message]
2023-03-16 14:26 ` [PATCH 0/2] KVM: x86: Fix kvm/queue breakage on clang Paolo Bonzini
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=b98945f0-09ef-158a-9348-e518469ec7e3@redhat.com \
--to=eesposit@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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