From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
"Gioh Kim" <gi-oh.kim@profitbricks.com>
Cc: joro@8bytes.org, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: ignore type when setting segment registers
Date: Tue, 30 May 2017 18:04:53 +0200 [thread overview]
Message-ID: <097f01c9-584e-01d9-43e9-35bee478a1e0@redhat.com> (raw)
In-Reply-To: <20170530150546.GB18926@potion>
On 30/05/2017 17:05, Radim Krčmář wrote:
> 2017-05-30 15:24+0200, Gioh Kim:
>> This patch is based on linux-next v4.12.0-rc3.
>
> (I'd omit this.)
>
>> Signed-off-by: Gioh Kim <gi-oh.kim@profitbricks.com>
>> ---
>
> Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
Queued, thanks.
Paolo
prev parent reply other threads:[~2017-05-30 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 13:24 [PATCH] KVM: SVM: ignore type when setting segment registers Gioh Kim
2017-05-30 15:05 ` Radim Krčmář
2017-05-30 16:04 ` 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=097f01c9-584e-01d9-43e9-35bee478a1e0@redhat.com \
--to=pbonzini@redhat.com \
--cc=gi-oh.kim@profitbricks.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.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).