public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	rostedt@goodmis.org, "Paul E. McKenney" <paulmck@kernel.org>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-pm@vger.kernel.org
Subject: [PATCH rcu 16/27] drivers/opp: Remove "select SRCU"
Date: Wed,  4 Jan 2023 16:38:02 -0800	[thread overview]
Message-ID: <20230105003813.1770367-16-paulmck@kernel.org> (raw)
In-Reply-To: <20230105003759.GA1769545@paulmck-ThinkPad-P17-Gen-1>

Now that the SRCU Kconfig option is unconditionally selected, there is
no longer any point in selecting it.  Therefore, remove the "select SRCU"
Kconfig statements.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Cc: Viresh Kumar <vireshk@kernel.org>
Cc: Nishanth Menon <nm@ti.com>
Cc: Stephen Boyd <sboyd@kernel.org>
Cc: <linux-pm@vger.kernel.org>
---
 drivers/opp/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/opp/Kconfig b/drivers/opp/Kconfig
index e8ce47b327359..d7c649a1a981c 100644
--- a/drivers/opp/Kconfig
+++ b/drivers/opp/Kconfig
@@ -1,7 +1,6 @@
 # SPDX-License-Identifier: GPL-2.0-only
 config PM_OPP
 	bool
-	select SRCU
 	help
 	  SOCs have a standard set of tuples consisting of frequency and
 	  voltage pairs that the device will support per voltage domain. This
-- 
2.31.1.189.g2e36527f23


  parent reply	other threads:[~2023-01-05  0:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230105003759.GA1769545@paulmck-ThinkPad-P17-Gen-1>
2023-01-05  0:37 ` [PATCH rcu 10/27] drivers/cpufreq: Remove "select SRCU" Paul E. McKenney
2023-01-05  4:04   ` Viresh Kumar
2023-01-05 15:09   ` Rafael J. Wysocki
2023-01-05 15:51     ` Paul E. McKenney
2023-01-05  0:37 ` [PATCH rcu 12/27] drivers/devfreq: " Paul E. McKenney
2023-01-10 13:07   ` Chanwoo Choi
2023-01-10 15:01     ` Paul E. McKenney
2023-01-05  0:38 ` Paul E. McKenney [this message]
2023-01-05  4:06   ` [PATCH rcu 16/27] drivers/opp: " Viresh Kumar
2023-01-05  4:50     ` Paul E. McKenney
2023-01-05  6:17   ` Viresh Kumar
2023-01-05 15:28     ` Paul E. McKenney
2023-01-05  0:38 ` [PATCH rcu 23/27] kernel/power: " Paul E. McKenney
2023-01-05 15:08   ` Rafael J. Wysocki

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=20230105003813.1770367-16-paulmck@kernel.org \
    --to=paulmck@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sboyd@kernel.org \
    --cc=vireshk@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