All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: rafael@kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mark Pearson <mpearson-lenovo@squebb.ca>,
	"Mario Limonciello (AMD)" <superm1@kernel.org>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] platform profile: Restrict the core prompt to COMPILE_TEST
Date: Wed, 18 Nov 2026 12:02:54 +0100	[thread overview]
Message-ID: <20261118110255.2946563-1-daniel.lezcano@oss.qualcomm.com> (raw)

All platform profile providers select PLATFORM_PROFILE, so users do not
need to enable the core explicitly.

Only show its prompt when COMPILE_TEST is enabled. This avoids exposing
the option in normal configurations while allowing the architecture-independent
core to be build-tested without a provider.

Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
---
 drivers/platform/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/platform/Kconfig b/drivers/platform/Kconfig
index 7270f24a3b6e..1cf87904afc3 100644
--- a/drivers/platform/Kconfig
+++ b/drivers/platform/Kconfig
@@ -1,6 +1,6 @@
 # SPDX-License-Identifier: GPL-2.0-only
 config PLATFORM_PROFILE
-	tristate "Platform profile support"
+	tristate "Platform profile support" if COMPILE_TEST
 	help
 	  Provide a common sysfs interface for selecting platform power,
 	  performance and cooling profiles. Platform-specific provider drivers
-- 
2.43.0


             reply	other threads:[~2026-11-18 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 11:02 Daniel Lezcano [this message]
2026-11-18 14:33 ` [PATCH] platform profile: Restrict the core prompt to COMPILE_TEST Mario Limonciello
2026-11-18 15:43 ` Mark Pearson
2026-11-18 15:58 ` Rafael J. Wysocki (Intel)

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=20261118110255.2946563-1-daniel.lezcano@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=superm1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.