From: Ben Hutchings <ben@decadent.org.uk>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH 0/7] KVM fixes for 3.2.17
Date: Tue, 22 May 2012 03:12:23 +0100 [thread overview]
Message-ID: <1337652743.11796.0.camel@deadeye> (raw)
In-Reply-To: <cover.1337374525.git.mtosatti@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
On Fri, 2012-05-18 at 17:58 -0300, Marcelo Tosatti wrote:
> See individual patches for details.
[...]
These came a little too late for 3.2.18, but I've queued them up now.
Ben.
--
Ben Hutchings
You can't have everything. Where would you put it?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-05-22 2:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 20:58 [PATCH 0/7] KVM fixes for 3.2.17 Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 1/7] KVM: mmu_notifier: Flush TLBs before releasing mmu_lock Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 2/7] KVM: Ensure all vcpus are consistent with in-kernel irqchip settings Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 3/7] KVM: lock slots_lock around device assignment Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 4/7] KVM: nVMX: Fix erroneous exception bitmap check Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 5/7] KVM: VMX: vmx_set_cr0 expects kvm->srcu locked Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 6/7] KVM: s390: do store status after handling STOP_ON_STOP bit Marcelo Tosatti
2012-05-18 20:58 ` [PATCH 7/7] KVM: s390: Sanitize fpc registers for KVM_SET_FPU Marcelo Tosatti
2012-05-22 2:12 ` Ben Hutchings [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=1337652743.11796.0.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=stable@vger.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).