From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-sunxi@lists.linux.dev, dri-devel@lists.freedesktop.org,
lkft-triage@lists.linaro.org
Cc: Maxime Ripard <mripard@kernel.org>,
Dave Airlie <airlied@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: arm: ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined!
Date: Mon, 4 Mar 2024 13:37:29 +0530 [thread overview]
Message-ID: <CA+G9fYvG9KE15PGNoLu+SBVyShe+u5HBLQ81+kK9Zop6u=ywmw@mail.gmail.com> (raw)
The arm defconfig builds failed on today's Linux next tag next-20240304.
Build log:
---------
ERROR: modpost: "__aeabi_uldivmod"
[drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined!
Steps to reproduce:
# tuxmake --runtime podman --target-arch arm --toolchain clang-17
--kconfig defconfig LLVM=1 LLVM_IAS=1
Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/history/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/log
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919744/suite/build/test/clang-17-defconfig/details/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-03-04 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:07 Naresh Kamboju [this message]
2024-03-04 11:11 ` arm: ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/sun4i/sun4i-drm-hdmi.ko] undefined! Arnd Bergmann
2024-03-04 11:24 ` Andre Przywara
2024-03-04 11:26 ` Arnd Bergmann
2024-03-04 11:45 ` Andre Przywara
2024-03-04 12:34 ` Arnd Bergmann
2024-03-04 13:01 ` Ard Biesheuvel
2024-03-04 13:48 ` Arnd Bergmann
2024-03-04 13:55 ` Ard Biesheuvel
2024-03-04 11:46 ` Maxime Ripard
2024-03-09 14:33 ` David Laight
2024-03-14 9:27 ` Geert Uytterhoeven
2024-03-14 11:14 ` Geert Uytterhoeven
2024-03-14 15:04 ` Maxime Ripard
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='CA+G9fYvG9KE15PGNoLu+SBVyShe+u5HBLQ81+kK9Zop6u=ywmw@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=airlied@redhat.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lkft-triage@lists.linaro.org \
--cc=mripard@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).