From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
skannan@codeaurora.org, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V2 0/5] cpufreq: sysfs cleanup
Date: Thu, 15 Oct 2015 21:35:20 +0530 [thread overview]
Message-ID: <cover.1444924623.git.viresh.kumar@linaro.org> (raw)
Rafael,
This is in response to the other thread where you and Saravana were
discussing this. It doesn't allow updating policy for offline CPUs yet,
but does cleanup the sysfs stuff.
This is untested by me as I didn't had access to the hardware to test
this week. But this is tested by Fengguang's build bot for some time
now.
Will be good if one of you can test this out.
V1->V2:
- Change log updated for the first patch
- One patch already applied and the last one is a new patch based on
Saravana's comments.
- Reviewed-by tags from Saravana.
Viresh Kumar (5):
cpufreq: Use cpumask_copy instead of cpumask_or to copy a mask
cpufreq: create cpu/cpufreq at boot time
cpufreq: remove cpufreq_sysfs_{create|remove}_file()
cpufreq: create cpu/cpufreq/policyX directories
cpufreq: postfix policy directory with the first CPU in related_cpus
drivers/cpufreq/cpufreq.c | 103 +++++++------------------------------
drivers/cpufreq/cpufreq_governor.c | 20 ++-----
include/linux/cpufreq.h | 5 --
3 files changed, 24 insertions(+), 104 deletions(-)
--
2.4.0
next reply other threads:[~2015-10-15 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 16:05 Viresh Kumar [this message]
2015-10-15 16:05 ` [PATCH V2 1/5] cpufreq: Use cpumask_copy instead of cpumask_or to copy a mask Viresh Kumar
2015-10-15 16:05 ` [PATCH V2 2/5] cpufreq: create cpu/cpufreq at boot time Viresh Kumar
2015-10-15 16:05 ` [PATCH V2 3/5] cpufreq: remove cpufreq_sysfs_{create|remove}_file() Viresh Kumar
2015-10-15 16:05 ` [PATCH V2 4/5] cpufreq: create cpu/cpufreq/policyX directories Viresh Kumar
2015-10-15 19:25 ` Saravana Kannan
2015-10-15 21:35 ` Rafael J. Wysocki
2015-10-16 5:51 ` Viresh Kumar
2015-10-28 8:16 ` Rafael J. Wysocki
2015-10-28 8:28 ` Viresh Kumar
2015-10-15 16:05 ` [PATCH V2 5/5] cpufreq: postfix policy directory with the first CPU in related_cpus Viresh Kumar
2015-10-15 19:14 ` Saravana Kannan
2015-10-16 7:08 ` Viresh Kumar
2015-10-16 7:11 ` [PATCH V3 " Viresh Kumar
2015-10-16 19:50 ` Saravana Kannan
2015-10-17 4:29 ` Viresh Kumar
2015-10-22 1:55 ` [PATCH V2 0/5] cpufreq: sysfs cleanup Viresh Kumar
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=cover.1444924623.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=skannan@codeaurora.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;
as well as URLs for NNTP newsgroup(s).