From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [GIT PULL] KVM updates for the 2.6.37 merge window
Date: Tue, 26 Oct 2010 18:42:14 +0200 [thread overview]
Message-ID: <4CC704E6.2060906@redhat.com> (raw)
In-Reply-To: <AAAC8548-D406-4CAC-8579-D2B5AAB6AC2C@suse.de>
On 10/26/2010 05:55 PM, Alexander Graf wrote:
> > Alex, if you want them in, please prepare backports for 2.6.36.1.
>
> Why backports for 2.6.36.1 when we're talking about 2.6.27? Most of them fix bugs introduced by the PV framework.
I should have said 2.6.37-rc1, sorry.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-10-26 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 13:29 [GIT PULL] KVM updates for the 2.6.37 merge window Avi Kivity
2010-10-24 23:28 ` Stephen Rothwell
2010-10-25 16:49 ` Scott Wood
2010-10-25 16:59 ` Avi Kivity
2010-10-26 15:55 ` Alexander Graf
2010-10-26 16:42 ` Avi Kivity [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=4CC704E6.2060906@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=scottwood@freescale.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.