From: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
To: Borislav Petkov <bp@alien8.de>,
<linux-stm32@st-md-mailman.stormreply.com>
Cc: Yannick Fertre <yannick.fertre@foss.st.com>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: dw_mipi_dsi-stm.c:(.text+0x8db9a3): undefined reference to `clk_hw_unregister'
Date: Mon, 9 Sep 2024 08:57:57 +0200 [thread overview]
Message-ID: <544a633e-de53-493d-9c29-de8ff52630da@foss.st.com> (raw)
In-Reply-To: <20240905081902.GAZtlpdlQp5XOm5XtO@fat_crate.local>
On 9/5/24 10:19, Borislav Petkov wrote:
> Hi all,
>
> this fires in my randbuilds here:
>
> vmlinux.o: warning: objtool: adis16400_write_raw() falls through to next function adis16400_show_serial_number()
> ld: vmlinux.o: in function `dw_mipi_dsi_stm_remove':
> dw_mipi_dsi-stm.c:(.text+0x8db9a3): undefined reference to `clk_hw_unregister'
> ld: vmlinux.o: in function `dw_mipi_dsi_clk_register':
> dw_mipi_dsi-stm.c:(.text+0x8db9f5): undefined reference to `clk_hw_register'
> ld: vmlinux.o: in function `lvds_remove':
> lvds.c:(.text+0x8dc605): undefined reference to `clk_hw_unregister'
> make[2]: *** [scripts/Makefile.vmlinux:34: vmlinux] Error 1
> make[1]: *** [/home/amd/bpetkov/kernel/linux/Makefile:1156: vmlinux] Error 2
> make: *** [Makefile:224: __sub-make] Error 2
>
> is there a fix somewhere?
Hi Borislav,
Arnd Bergmann sent a patch regarding this issue on x86 that I merged several
weeks ago.
https://lore.kernel.org/lkml/20240719075454.3595358-1-arnd@kernel.org/
https://lore.kernel.org/all/c3d0757a-07c0-4f83-9f06-c3ad205aa1e9@foss.st.com/
>
> People love to do
>
> depends on ... COMPILE_TEST
>
> but then if no one takes care of it in time:
>
> https://lore.kernel.org/oe-kbuild-all/202407212000.rpDH64jP-lkp@intel.com
Now, I'm not familiar with PowerPC architecture and toolchains, but I think this
patch should fix your problem.
Do you have the above fixup in your tree ? If not please try it.
Thanks,
Regards,
Raphaël
>
> that COMPILE_TEST thing is forcing me to simply blacklist it and is not really
> helping.
>
> Thx.
>
next prev parent reply other threads:[~2024-09-09 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:19 Borislav Petkov
2024-09-09 6:57 ` Raphael Gallais-Pou [this message]
2024-09-09 8:45 ` Borislav Petkov
2024-09-10 10:48 ` Raphael Gallais-Pou
2024-09-10 11:06 ` Borislav Petkov
2024-09-10 11:59 ` Maxime Ripard
2024-09-10 12:13 ` Raphael Gallais-Pou
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=544a633e-de53-493d-9c29-de8ff52630da@foss.st.com \
--to=raphael.gallais-pou@foss.st.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=bp@alien8.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=philippe.cornu@foss.st.com \
--cc=tzimmermann@suse.de \
--cc=yannick.fertre@foss.st.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®