Linux Power Management development
 help / color / mirror / Atom feed
From: Kevin Hao <haokexin@gmail.com>
To: linux-pm@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 2/3] cpufreq: schedutil: Use to_gov_attr_set() to get the gov_attr_set
Date: Sun, 23 Jan 2022 20:45:07 +0800	[thread overview]
Message-ID: <20220123124508.463305-2-haokexin@gmail.com> (raw)
In-Reply-To: <20220123124508.463305-1-haokexin@gmail.com>

The to_gov_attr_set() has been moved to the cpufreq.h, so use it to get
the gov_attr_set.

Signed-off-by: Kevin Hao <haokexin@gmail.com>
---
 kernel/sched/cpufreq_schedutil.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index 26778884d9ab..cffcd08f4ec8 100644
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -539,7 +539,7 @@ ATTRIBUTE_GROUPS(sugov);
 
 static void sugov_tunables_free(struct kobject *kobj)
 {
-	struct gov_attr_set *attr_set = container_of(kobj, struct gov_attr_set, kobj);
+	struct gov_attr_set *attr_set = to_gov_attr_set(kobj);
 
 	kfree(to_sugov_tunables(attr_set));
 }
-- 
2.31.1


  reply	other threads:[~2022-01-23 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 12:45 [PATCH 1/3] cpufreq: Move to_gov_attr_set() to cpufreq.h Kevin Hao
2022-01-23 12:45 ` Kevin Hao [this message]
2022-01-23 12:45 ` [PATCH 3/3] cpufreq: governor: Use kobject release() method to free dbs_data Kevin Hao
2022-02-04 18:19   ` Rafael J. Wysocki
2022-02-05 11:01     ` Kevin Hao
2022-04-09 12:10       ` Kevin Hao
2022-04-13 13:30         ` Rafael J. Wysocki
2022-02-04 18:25 ` [PATCH 1/3] cpufreq: Move to_gov_attr_set() to cpufreq.h 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=20220123124508.463305-2-haokexin@gmail.com \
    --to=haokexin@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.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