From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Xingxing Su <suxingxing@loongson.cn>,
Huacai Chen <chenhc@lemote.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] KVM: MIPS/VZ: Fix build error caused by 'kvm_run' cleanup
Date: Tue, 11 Aug 2020 22:37:00 +0800 [thread overview]
Message-ID: <49a63b59-c03e-b9f5-03d6-ef268f5a6555@flygoat.com> (raw)
In-Reply-To: <1597138297-2105-1-git-send-email-suxingxing@loongson.cn>
在 2020/8/11 下午5:31, Xingxing Su 写道:
> Commit c34b26b98caca48ec9ee9 ("KVM: MIPS: clean up redundant 'kvm_run'
> parameters") remove the 'kvm_run' parameter in kvm_vz_gpsi_lwc2.
>
> The following build error:
>
> arch/mips/kvm/vz.c: In function ‘kvm_trap_vz_handle_gpsi’:
> arch/mips/kvm/vz.c:1243:43: error: ‘run’ undeclared (first use in this function)
> er = kvm_vz_gpsi_lwc2(inst, opc, cause, run, vcpu);
> ^~~
> arch/mips/kvm/vz.c:1243:43: note: each undeclared identifier is reported only
> once for each function it appears in
> scripts/Makefile.build:283: recipe for target 'arch/mips/kvm/vz.o' failed
> make[2]: *** [arch/mips/kvm/vz.o] Error 1
> scripts/Makefile.build:500: recipe for target 'arch/mips/kvm' failed
> make[1]: *** [arch/mips/kvm] Error 2
> Makefile:1785: recipe for target 'arch/mips' failed
> make: *** [arch/mips] Error 2
>
> Signed-off-by: Xingxing Su <suxingxing@loongson.cn>
That have already quened in Paolo's KVM tree.
Thanks.
- Jiaxun
> ---
> +cc Paolo Bonzini <pbonzini@redhat.com> and kvm@vger.kernel.org.
>
>
next prev parent reply other threads:[~2020-08-11 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 9:31 [PATCH RESEND] KVM: MIPS/VZ: Fix build error caused by 'kvm_run' cleanup Xingxing Su
2020-08-11 11:19 ` Paolo Bonzini
2020-08-11 14:37 ` Jiaxun Yang [this message]
2020-08-11 14:38 ` Jiaxun Yang
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=49a63b59-c03e-b9f5-03d6-ef268f5a6555@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=chenhc@lemote.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=suxingxing@loongson.cn \
--cc=tsbogend@alpha.franken.de \
/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