From: "tip-bot2 for Borislav Petkov (AMD)" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: "Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/core] x86/bugs: Fix indentation due to ITS merge
Date: Fri, 16 May 2025 14:46:44 -0000 [thread overview]
Message-ID: <174740680468.406.372152086131806707.tip-bot2@tip-bot2> (raw)
The following commit has been merged into the x86/core branch of tip:
Commit-ID: ff8f7a889abd9741abde6e83d33a3a7d9d6e7d83
Gitweb: https://git.kernel.org/tip/ff8f7a889abd9741abde6e83d33a3a7d9d6e7d83
Author: Borislav Petkov (AMD) <bp@alien8.de>
AuthorDate: Fri, 16 May 2025 16:31:38 +02:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Fri, 16 May 2025 16:31:38 +02:00
x86/bugs: Fix indentation due to ITS merge
No functional changes.
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
---
arch/x86/kernel/cpu/bugs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
index dd8b50b..d1a03ff 100644
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -2975,10 +2975,10 @@ static void __init srso_apply_mitigation(void)
if (boot_cpu_data.x86 == 0x19) {
setup_force_cpu_cap(X86_FEATURE_SRSO_ALIAS);
- set_return_thunk(srso_alias_return_thunk);
+ set_return_thunk(srso_alias_return_thunk);
} else {
setup_force_cpu_cap(X86_FEATURE_SRSO);
- set_return_thunk(srso_return_thunk);
+ set_return_thunk(srso_return_thunk);
}
break;
case SRSO_MITIGATION_IBPB:
next reply other threads:[~2025-05-16 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 14:46 tip-bot2 for Borislav Petkov (AMD) [this message]
2025-05-16 15:38 ` [PATCH] x86/bugs: Apply misc stylistic touchups Ingo Molnar
2025-05-16 15:48 [tip: x86/core] x86/bugs: Fix indentation due to ITS merge tip-bot2 for Borislav Petkov (AMD)
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=174740680468.406.372152086131806707.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=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®