From: Jens Axboe <axboe@kernel.dk>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: vmx: rename pi_init to avoid conflict with paride
Date: Sat, 24 Oct 2020 09:18:36 -0600 [thread overview]
Message-ID: <224b8101-6829-0948-864a-95c403db3b51@kernel.dk> (raw)
In-Reply-To: <20201024081024.2798990-1-pbonzini@redhat.com>
On 10/24/20 2:10 AM, Paolo Bonzini wrote:
> allyesconfig results in:
>
> ld: drivers/block/paride/paride.o: in function `pi_init':
> (.text+0x1340): multiple definition of `pi_init'; arch/x86/kvm/vmx/posted_intr.o:posted_intr.c:(.init.text+0x0): first defined here
> make: *** [Makefile:1164: vmlinux] Error 1
>
> because commit:
>
> commit 8888cdd0996c2d51cd417f9a60a282c034f3fa28
> Author: Xiaoyao Li <xiaoyao.li@intel.com>
> Date: Wed Sep 23 11:31:11 2020 -0700
>
> KVM: VMX: Extract posted interrupt support to separate files
>
> added another pi_init(), though one already existed in the paride code.
Thanks, works for me.
--
Jens Axboe
prev parent reply other threads:[~2020-10-24 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 8:10 [PATCH] KVM: vmx: rename pi_init to avoid conflict with paride Paolo Bonzini
2020-10-24 15:18 ` Jens Axboe [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=224b8101-6829-0948-864a-95c403db3b51@kernel.dk \
--to=axboe@kernel.dk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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).