From: Michael Ellerman <mpe@ellerman•id.au>
To: Naresh Kamboju <naresh.kamboju@linaro•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
open list <linux-kernel@vger•kernel.org>
Cc: Claudio Imbrenda <imbrenda@linux•ibm.com>,
Marc Zyngier <maz@kernel•org>,
Paolo Bonzini <pbonzini@redhat•com>,
Sean Christopherson <seanjc@google•com>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle•com>,
lkft-triage@lists•linaro.org
Subject: Re: [next] powerpc: book3s_hv.c:4591:27: error: 'struct kvm_vcpu' has no member named 'wait'
Date: Thu, 16 Dec 2021 16:25:05 +1100 [thread overview]
Message-ID: <87o85hktou.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CA+G9fYua-LEU7u3OA0=c8HnBjoU6WENh9Avc18GGLg8Dbf9ZAw@mail.gmail.com>
Naresh Kamboju <naresh.kamboju@linaro•org> writes:
> [ Please ignore this email if it is already reported ]
>
> While building Linux next 20211214 powerpc defconfig with gcc-8/9/10/11
> following warnings / errors noticed.
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/current ARCH=powerpc
> CROSS_COMPILE=powerpc64le-linux-gnu- 'CC=sccache
> powerpc64le-linux-gnu-gcc' 'HOSTCC=sccache gcc'
> 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);
> ^~
> make[3]: *** [scripts/Makefile.build:289: arch/powerpc/kvm/book3s_hv.o] Error 1
>
> meta data:
> -----------
> git describe: next-20211214
Should be fixed in next-20211215 by:
63fa47ba886b ("KVM: PPC: Book3S HV P9: Use kvm_arch_vcpu_get_wait() to get rcuwait object")
cheers
prev parent reply other threads:[~2021-12-16 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 12:22 [next] powerpc: book3s_hv.c:4591:27: error: 'struct kvm_vcpu' has no member named 'wait' Naresh Kamboju
2021-12-16 5:25 ` Michael Ellerman [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=87o85hktou.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=imbrenda@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=maciej.szmigiero@oracle$(echo .)com \
--cc=maz@kernel$(echo .)org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=pbonzini@redhat$(echo .)com \
--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