From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Sachin Sant <sachinp@in.ibm.com>,
linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: KVM: fix S390/IA-64 build failures introduced by memslot changes
Date: Tue, 12 Jan 2010 14:08:18 +0200 [thread overview]
Message-ID: <4B4C6632.9090109@redhat.com> (raw)
In-Reply-To: <20100111172309.GA13797@amt.cnet>
On 01/11/2010 07:23 PM, Marcelo Tosatti wrote:
> Fix build failures introduced by memslot changes.
>
Thanks, applied, and folded back into relevant kvm-updates/2.6.34 commits.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-12 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 8:44 linux-next: Tree for January 11 Stephen Rothwell
2010-01-11 10:15 ` -next Jan 11 : s390/kvm build failure Sachin Sant
2010-01-11 10:32 ` Avi Kivity
2010-01-11 17:23 ` KVM: fix S390/IA-64 build failures introduced by memslot changes Marcelo Tosatti
2010-01-12 12:08 ` 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=4B4C6632.9090109@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sachinp@in.ibm.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).