linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: linux-s390@vger.kernel.org
Cc: linux-next@vger.kernel.org, kvm@vger.kernel.org, mtosatti@redhat.com
Subject: -next Jan 11 : s390/kvm build failure
Date: Mon, 11 Jan 2010 15:45:33 +0530	[thread overview]
Message-ID: <4B4AFA45.8000004@in.ibm.com> (raw)
In-Reply-To: <20100111194431.c103db9b.sfr@canb.auug.org.au>

Today's next build on s390 failed with:

In file included from arch/s390/kvm/kvm-s390.c:30:
arch/s390/kvm/kvm-s390.h: In function 'kvm_s390_vcpu_set_mem':
arch/s390/kvm/kvm-s390.h:75: warning: assignment from incompatible pointer type
arch/s390/kvm/kvm-s390.h:77: error: dereferencing pointer to incomplete type
arch/s390/kvm/kvm-s390.c: At top level:
arch/s390/kvm/kvm-s390.c:692: error: conflicting types for 'kvm_arch_prepare_memory_region'
include/linux/kvm_host.h:258: error: previous declaration of 'kvm_arch_prepare_memory_region' was here
arch/s390/kvm/kvm-s390.c: In function 'kvm_arch_prepare_memory_region':
arch/s390/kvm/kvm-s390.c:698: warning: unused variable 'vcpu'
arch/s390/kvm/kvm-s390.c:697: warning: unused variable 'i'
arch/s390/kvm/kvm-s390.c: At top level:
arch/s390/kvm/kvm-s390.c:725: error: conflicting types for 'kvm_arch_commit_memory_region'
include/linux/kvm_host.h:262: error: previous declaration of 'kvm_arch_commit_memory_region' was here
arch/s390/kvm/kvm-s390.c: In function 'kvm_arch_commit_memory_region':
arch/s390/kvm/kvm-s390.c:731: error: 'i' undeclared (first use in this function)
arch/s390/kvm/kvm-s390.c:731: error: (Each undeclared identifier is reported only once
arch/s390/kvm/kvm-s390.c:731: error: for each function it appears in.)
arch/s390/kvm/kvm-s390.c:731: error: 'vcpu' undeclared (first use in this function)
arch/s390/kvm/kvm-s390.c:731: warning: left-hand operand of comma expression has no effect

and few more 

In file included from arch/s390/kvm/intercept.c:20:
arch/s390/kvm/kvm-s390.h: In function 'kvm_s390_vcpu_set_mem':
arch/s390/kvm/kvm-s390.h:75: warning: assignment from incompatible pointer type
arch/s390/kvm/kvm-s390.h:77: error: dereferencing pointer to incomplete type
make[1]: *** [arch/s390/kvm/intercept.o] Error 1

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

Thanks
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

  reply	other threads:[~2010-01-11 10:15 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 ` Sachin Sant [this message]
2010-01-11 10:32   ` -next Jan 11 : s390/kvm build failure 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

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=4B4AFA45.8000004@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.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).