[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250729114037.03a2d884@canb.auug.org.au>
Date: Tue, 29 Jul 2025 11:40:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Donghoon Yu <hoony.yu@...sung.com>, Will McVicker
<willmcvicker@...gle.com>, Youngmin Nam <youngmin.nam@...sung.com>, Linux
Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo
Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra
<peterz@...radead.org>
Subject: Re: linux-next: build warning after merge of the clockevents tree
Hi all,
On Wed, 16 Jul 2025 16:08:09 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the clockevents tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: mct_init_dt+0x324 (section: .text) -> register_current_timer_delay (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: mct_init_dt+0x4c4 (section: .text) -> register_current_timer_delay (section: .init.text)
>
> Introduced by commit
>
> 5d86e479193b ("clocksource/drivers/exynos_mct: Add module support")
>
> and possibly
>
> 7e477e9c4eb4 ("clocksource/drivers/exynos_mct: Fix section mismatch from the module conversion")
>
> For this build,
>
> CONFIG_CLKSRC_EXYNOS_MCT=y
I am still seeing these warnings. The above commit is now also commit
338007c44c7f ("clocksource/drivers/exynos_mct: Add module support")
in the tip tree.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists