From: Paolo Bonzini <pbonzini@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
thomas.lendacky@amd.com, fwilhelm@google.com,
kvm list <kvm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
oupton@google.com, Sean Christopherson <seanjc@google.com>,
linux-stable <stable@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 1/8] KVM: SEV-ES: fix length of string I/O
Date: Mon, 18 Oct 2021 12:54:01 +0200 [thread overview]
Message-ID: <3da8fd50-bdb3-93bd-3d27-0b3f961bd531@redhat.com> (raw)
In-Reply-To: <CA+G9fYt7FMXbp47ObVZ4B7X917186Fu39+LM04PcbqZ2-f7-qg@mail.gmail.com>
On 18/10/21 12:21, Naresh Kamboju wrote:
> [Please ignore this email if it already reported ]
>
> Following build errors noticed while building Linux next 20211018
> with gcc-11 for i386 architecture.
>
> i686-linux-gnu-ld: arch/x86/kvm/svm/sev.o: in function `sev_es_string_io':
> sev.c:(.text+0x110f): undefined reference to `__udivdi3'
> make[1]: *** [/builds/linux/Makefile:1247: vmlinux] Error 1
> make[1]: Target '__all' not remade because of errors.
> make: *** [Makefile:226: __sub-make] Error 2
Thank you very much, I have sent a simple fix of changing the variable
to u32.
Paolo
next prev parent reply other threads:[~2021-10-18 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 10:21 Naresh Kamboju
2021-10-18 10:54 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-13 16:56 [PATCH 0/8] KVM: SEV-ES: fixes for string I/O emulation Paolo Bonzini
2021-10-13 16:56 ` [PATCH 1/8] KVM: SEV-ES: fix length of string I/O Paolo Bonzini
2021-10-14 20:13 ` Tom Lendacky
2021-10-21 23:10 ` Maxim Levitsky
2021-10-25 1:31 ` Marc Orr
2021-10-25 8:59 ` Paolo Bonzini
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=3da8fd50-bdb3-93bd-3d27-0b3f961bd531@redhat.com \
--to=pbonzini@redhat.com \
--cc=fwilhelm@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=oupton@google.com \
--cc=seanjc@google.com \
--cc=sfr@canb.auug.org.au \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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
all inboxes | Powered by JetHome®