public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rong Xu <xur@google.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
	Yabin Cui <yabinc@google.com>,  Will Deacon <will@kernel.org>,
	Han Shen <shenhan@google.com>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Kees Cook <kees@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	 Alice Ryhl <aliceryhl@google.com>,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	 Samuel Holland <samuel.holland@sifive.com>,
	"Paul E. McKenney" <paulmck@kernel.org>, Rong Xu <xur@google.com>,
	 Arnd Bergmann <arnd@arndb.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] Propeller: Remove the architecture specific config
Date: Wed, 11 Dec 2024 14:29:43 -0800	[thread overview]
Message-ID: <20241211222945.1325793-2-xur@google.com> (raw)
In-Reply-To: <20241211222945.1325793-1-xur@google.com>

The CONFIG_PROPELLER_CLANG option currently depends on
ARCH_SUPPORTS_PROPELLER_CLANG, but this dependency seems unnecessary.

Remove ARCH_SUPPORTS_PROPELLER_CLANG and allow users to control
Propeller builds solely through CONFIG_PROPELLER_CLANG. This simplifies
the kconfig and avoids potential confusion.

Signed-off-by: Rong Xu <xur@google.com>
Suggested-by: Will Deacon <will@kernel.org>
---
 arch/Kconfig     | 4 ----
 arch/x86/Kconfig | 1 -
 2 files changed, 5 deletions(-)

diff --git a/arch/Kconfig b/arch/Kconfig
index 0b36d74d47031..83731b858ba65 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -828,12 +828,8 @@ config AUTOFDO_CLANG
 
 	  If unsure, say N.
 
-config ARCH_SUPPORTS_PROPELLER_CLANG
-	bool
-
 config PROPELLER_CLANG
 	bool "Enable Clang's Propeller build"
-	depends on ARCH_SUPPORTS_PROPELLER_CLANG
 	depends on CC_IS_CLANG && CLANG_VERSION >= 190000
 	help
 	  This option enables Clang’s Propeller build. When the Propeller
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 9363d9cc9a00a..6c633d93c6390 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -128,7 +128,6 @@ config X86
 	select ARCH_SUPPORTS_LTO_CLANG
 	select ARCH_SUPPORTS_LTO_CLANG_THIN
 	select ARCH_SUPPORTS_RT
-	select ARCH_SUPPORTS_PROPELLER_CLANG    if X86_64
 	select ARCH_USE_BUILTIN_BSWAP
 	select ARCH_USE_CMPXCHG_LOCKREF		if X86_CMPXCHG64
 	select ARCH_USE_MEMTEST
-- 
2.47.0.338.g60cca15819-goog


  reply	other threads:[~2024-12-11 22:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 22:29 [PATCH 1/2] AutoFDO: Remove the architecture specific config Rong Xu
2024-12-11 22:29 ` Rong Xu [this message]
2024-12-11 23:05   ` [PATCH 2/2] Propeller: " Nathan Chancellor
2024-12-12  7:48     ` Rong Xu
2025-01-31 22:36       ` Yabin Cui
2025-02-04 20:05   ` Kees Cook
2024-12-19 15:52 ` [PATCH 1/2] AutoFDO: " Will Deacon
2024-12-19 17:19   ` Rong Xu
2025-01-31 22:35     ` Yabin Cui
2025-02-04 20:04 ` Kees Cook

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=20241211222945.1325793-2-xur@google.com \
    --to=xur@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=rppt@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=samuel.holland@sifive.com \
    --cc=shenhan@google.com \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yabinc@google.com \
    /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