From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "gleb@redhat.com" <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"Ren, Qiaowei" <qiaowei.ren@intel.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM
Date: Tue, 21 Jan 2014 17:33:18 +0100 [thread overview]
Message-ID: <52DEA14E.2030602@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350149CB2D@SHSMSX101.ccr.corp.intel.com>
Il 21/01/2014 16:25, Liu, Jinsong ha scritto:
> Hmm? I remember I have sent out the rebased patches v3 last month
> If you didn't receive them I'm OK to rebase and resend them. BTW, what's
> the review remarks? I remember you commented that the patches are fine.
> Any misunderstanding please point out to me.
You sent v3 of QEMU, but not of KVM. I don't see any mail from you
after December 12th on kvm@vger.kernel.org.
I can see my comment that the patches were fine (apart from needing a
rebase), but the threading was wrong and I cannot find anymore _which_
patches they were. I did find a comment that BNDCFGS must be added to
msrs_to_save, but I don't know if that was v1 or v2 because you didn't
add the version number when sending v2.
Paolo
next prev parent reply other threads:[~2014-01-21 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1386394315-48984-1-git-send-email-jinsong.liu@intel.com>
2013-12-11 8:31 ` [Qemu-devel] [PATCH v2 0/4] X86/KVM: enable Intel MPX for KVM Liu, Jinsong
2013-12-11 9:53 ` Paolo Bonzini
2013-12-12 5:47 ` Liu, Jinsong
2013-12-12 9:43 ` Paolo Bonzini
2013-12-12 11:09 ` Liu, Jinsong
2014-01-20 14:35 ` Paolo Bonzini
2014-01-21 15:25 ` Liu, Jinsong
2014-01-21 16:33 ` Paolo Bonzini [this message]
2014-01-21 17:26 ` Liu, Jinsong
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=52DEA14E.2030602@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=qiaowei.ren@intel.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;
as well as URLs for NNTP newsgroup(s).