From: Avi Kivity <avi@redhat.com>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: -next Jan 11 : s390/kvm build failure
Date: Mon, 11 Jan 2010 12:32:06 +0200 [thread overview]
Message-ID: <4B4AFE26.5080503@redhat.com> (raw)
In-Reply-To: <4B4AFA45.8000004@in.ibm.com>
On 01/11/2010 12:15 PM, Sachin Sant wrote:
>
> Probable cause could be the following commits :
>
> commit a94db899e8e5b7c4d47e42982800243dcdc69a38
> KVM: split kvm_arch_set_memory_region into prepare and commit
>
> commit fe7701e1daa1ad09d5d271897b6cc65697d33db2
> KVM: switch vcpu context to use SRCU
>
Yes. Marcelo? ia64 suffers from the same issue.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-11 10:32 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 [this message]
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
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=4B4AFE26.5080503@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 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.