From: "tip-bot2 for Lukas Bulwahn" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cleanups] x86/Kconfig: Remove obsolete config X86_32_SMP
Date: Tue, 28 Nov 2023 14:17:12 -0000 [thread overview]
Message-ID: <170118103247.398.14904326110266831066.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20231128090016.29676-1-lukas.bulwahn@gmail.com>
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: c64545594daf748422fa083389b062d0a16fb477
Gitweb: https://git.kernel.org/tip/c64545594daf748422fa083389b062d0a16fb477
Author: Lukas Bulwahn <lukas.bulwahn@gmail.com>
AuthorDate: Tue, 28 Nov 2023 10:00:16 +01:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Tue, 28 Nov 2023 13:31:34 +01:00
x86/Kconfig: Remove obsolete config X86_32_SMP
Commit
0f08c3b22996 ("x86/smp: Reduce code duplication")
removed the only use of CONFIG_X86_32_SMP.
Remove the now obsolete config X86_32_SMP too.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20231128090016.29676-1-lukas.bulwahn@gmail.com
---
arch/x86/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 3762f41..5a6728d 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -384,10 +384,6 @@ config HAVE_INTEL_TXT
def_bool y
depends on INTEL_IOMMU && ACPI
-config X86_32_SMP
- def_bool y
- depends on X86_32 && SMP
-
config X86_64_SMP
def_bool y
depends on X86_64 && SMP
next prev parent reply other threads:[~2023-11-28 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 9:00 [PATCH RESEND] " Lukas Bulwahn
2023-11-28 14:17 ` tip-bot2 for Lukas Bulwahn [this message]
2023-11-28 16:28 ` Randy Dunlap
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=170118103247.398.14904326110266831066.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=lukas.bulwahn@gmail.com \
--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®