From: Sachin Sant <sachinp@linux•vnet.ibm.com>
To: kvm@vger•kernel.org, linuxppc-dev@lists•ozlabs.org
Cc: linux-next@vger•kernel.org, seanjc@google•com
Subject: [next-20211210] Build break powerpc/kvm: unknown member wait
Date: Sat, 11 Dec 2021 16:20:16 +0530 [thread overview]
Message-ID: <496ECBB3-36F3-4F07-83B2-875F683BC446@linux.vnet.ibm.com> (raw)
next-20211210 ( commit ea922272cbe547) powerpc build fails due to following error:
arch/powerpc/kvm/book3s_hv.c: In function 'kvmhv_run_single_vcpu':
arch/powerpc/kvm/book3s_hv.c:4591:27: error: 'struct kvm_vcpu' has no member named 'wait'
prepare_to_rcuwait(&vcpu->wait);
^~
arch/powerpc/kvm/book3s_hv.c:4608:23: error: 'struct kvm_vcpu' has no member named 'wait'
finish_rcuwait(&vcpu->wait);
^~
commit 510958e997217: KVM: Force PPC to define its own rcuwait object
introduced the error.
Thanks
-Sachin
next reply other threads:[~2021-12-11 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 10:50 Sachin Sant [this message]
2021-12-13 17:30 ` [next-20211210] Build break powerpc/kvm: unknown member wait Sean Christopherson
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=496ECBB3-36F3-4F07-83B2-875F683BC446@linux.vnet.ibm.com \
--to=sachinp@linux$(echo .)vnet.ibm.com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=seanjc@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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