[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251029123823.GAaQIKvz4gUk3Nsaj4@fat_crate.local>
Date: Wed, 29 Oct 2025 13:38:23 +0100
From: Borislav Petkov <bp@...en8.de>
To: Yu Peng <pengyu@...inos.cn>
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
	x86@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	Yu Peng <pengyu@...inos.com>
Subject: Re: [PATCH v2] arch/x86/microcode: Mark early_parse_cmdline() as
 __init
On Wed, Oct 29, 2025 at 04:16:44PM +0800, Yu Peng wrote:
> From: Yu Peng <pengyu@...inos.com>
> 
> Fix section mismatch warning reported by modpost:
>   .text:early_parse_cmdline() -> .init.data:boot_command_line
How do you trigger this?
CONFIG_DEBUG_SECTION_MISMATCH=y
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
in my config doesn't cause anything.
That's because
$ readelf -s vmlinux | grep early_parse_cmdline
doesn't give anything because my compiler inlines it anyway.
So it must be something about your .config or toolchain or whatnot, which
causes it.
I mean, the patch is obviously correct but I'd still like to know how it
triggers.
Thx.
-- 
Regards/Gruss,
    Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists
 
