From: Greg KH <greg@kroah.com>
To: Avi Kivity <avi@redhat.com>
Cc: stable@vger.kernel.org, kvm@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 0/4] KVM updates for Linux 3.1.8
Date: Thu, 12 Jan 2012 08:15:10 -0800 [thread overview]
Message-ID: <20120112161510.GA11287@kroah.com> (raw)
In-Reply-To: <1326364794-18150-1-git-send-email-avi@redhat.com>
On Thu, Jan 12, 2012 at 12:39:50PM +0200, Avi Kivity wrote:
> The following patches want to be applied to the 3.1 branch. "All users must
> update".
Do any of these also need to go to the 3.0 branch?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-12 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 10:39 [PATCH 0/4] KVM updates for Linux 3.1.8 Avi Kivity
2012-01-12 10:39 ` [PATCH 1/4] KVM guest: prevent tracing recursion with kvmclock Avi Kivity
2012-01-12 10:39 ` [PATCH 2/4] KVM: x86: Prevent starting PIT timers in the absence of irqchip support Avi Kivity
2012-01-12 10:39 ` [PATCH 3/4] KVM: Remove ability to assign a device without iommu support Avi Kivity
2012-01-12 10:39 ` [PATCH 4/4] KVM: Device assignment permission checks Avi Kivity
2012-01-12 16:15 ` Greg KH [this message]
2012-01-12 16:25 ` [PATCH 0/4] KVM updates for Linux 3.1.8 Avi Kivity
2012-01-12 22:58 ` Greg KH
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=20120112161510.GA11287@kroah.com \
--to=greg@kroah.com \
--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