From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: fanwenyi0529@gmail.com, rkrcmar@redhat.com
Subject: Re: [PATCH 0/2] KVM: nVMX: kmap() can't fail
Date: Wed, 25 Jan 2017 13:08:29 +0100 [thread overview]
Message-ID: <d5276555-a384-3ce6-b373-62cdacbdcf01@redhat.com> (raw)
In-Reply-To: <20170125105858.20850-1-david@redhat.com>
On 25/01/2017 11:58, David Hildenbrand wrote:
> Not sure if the second one is strictly needed (delta LOC changes is 0).
>
> David Hildenbrand (2):
> KVM: nVMX: kmap() can't fail
> KVM: nVMX: vmx_complete_nested_posted_interrupt() can't fail
>
> arch/x86/kvm/vmx.c | 19 +++++--------------
> 1 file changed, 5 insertions(+), 14 deletions(-)
>
It's okay since you're removing the cases with nonzero return value.
Queued, thanks.
Paolo
prev parent reply other threads:[~2017-01-25 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 10:58 [PATCH 0/2] KVM: nVMX: kmap() can't fail David Hildenbrand
2017-01-25 10:58 ` [PATCH 1/2] " David Hildenbrand
2017-01-25 10:58 ` [PATCH 2/2] KVM: nVMX: vmx_complete_nested_posted_interrupt() " David Hildenbrand
2017-01-25 12:08 ` 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=d5276555-a384-3ce6-b373-62cdacbdcf01@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@redhat.com \
--cc=fanwenyi0529@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=rkrcmar@redhat.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