mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Yu Peng" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Yu Peng <pengyu@kylinos.cn>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/microcode] x86/microcode: Mark early_parse_cmdline() as __init
Date: Thu, 30 Oct 2025 20:21:48 -0000	[thread overview]
Message-ID: <176185570829.2601451.17127553971644289493.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20251030123757.1410904-1-pengyu@kylinos.cn>

The following commit has been merged into the x86/microcode branch of tip:

Commit-ID:     ca8313fd83399ea1d18e695c2ae9b259985c9e1f
Gitweb:        https://git.kernel.org/tip/ca8313fd83399ea1d18e695c2ae9b259985c9e1f
Author:        Yu Peng <pengyu@kylinos.cn>
AuthorDate:    Thu, 30 Oct 2025 20:37:57 +08:00
Committer:     Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Thu, 30 Oct 2025 14:33:31 +01:00

x86/microcode: Mark early_parse_cmdline() as __init

Fix section mismatch warning reported by modpost:

  .text:early_parse_cmdline() -> .init.data:boot_command_line

The function early_parse_cmdline() is only called during init and accesses
init data, so mark it __init to match its usage.

  [ bp: This happens only when the toolchain fails to inline the function and
    I haven't been able to reproduce it with any toolchain I'm using. Patch is
    obviously correct regardless. ]

Signed-off-by: Yu Peng <pengyu@kylinos.cn>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://patch.msgid.link/all/20251030123757.1410904-1-pengyu@kylinos.cn
---
 arch/x86/kernel/cpu/microcode/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kernel/cpu/microcode/core.c b/arch/x86/kernel/cpu/microcode/core.c
index d7baec8..ccc83b0 100644
--- a/arch/x86/kernel/cpu/microcode/core.c
+++ b/arch/x86/kernel/cpu/microcode/core.c
@@ -136,7 +136,7 @@ bool __init microcode_loader_disabled(void)
 	return dis_ucode_ldr;
 }
 
-static void early_parse_cmdline(void)
+static void __init early_parse_cmdline(void)
 {
 	char cmd_buf[64] = {};
 	char *s, *p = cmd_buf;

      reply	other threads:[~2025-10-30 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  8:16 [PATCH v2] arch/x86/microcode: " Yu Peng
2025-10-29 12:38 ` Borislav Petkov
2025-10-30  5:03   ` Yu Peng
2025-10-30 13:23     ` Borislav Petkov
2025-10-30 12:37 ` [PATCH v4] " Yu Peng
2025-10-30 20:21   ` tip-bot2 for Yu Peng [this message]

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=176185570829.2601451.17127553971644289493.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=pengyu@kylinos.cn \
    --cc=x86@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

all inboxes | Powered by JetHome®