From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Stratos Karafotis <stratosk@semaphore.gr>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
Subject: [PATCH V2 0/3] cpufreq: Simplify freq limit handling
Date: Fri, 22 May 2026 09:49:07 +0530 [thread overview]
Message-ID: <cover.1779423281.git.viresh.kumar@linaro.org> (raw)
Hello,
Here is the second version of this patchset.
V2:
- Add tags from reviewers.
- Drop intel-pstate change.
Lifeng Zheng (1):
cpufreq: conservative: Simplify frequency limit handling
Viresh Kumar (2):
cpufreq: Fix typo in comment
cpufreq: Avoid redundant target() calls for unchanged limits
drivers/cpufreq/cpufreq.c | 31 ++++++++++++++++++--------
drivers/cpufreq/cpufreq_conservative.c | 12 +---------
include/linux/cpufreq.h | 5 ++++-
3 files changed, 27 insertions(+), 21 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2026-05-22 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 4:19 Viresh Kumar [this message]
2026-05-22 4:19 ` [PATCH V2 1/3] cpufreq: Fix typo in comment Viresh Kumar
2026-05-22 4:19 ` [PATCH V3 2/3] cpufreq: Avoid redundant target() calls for unchanged limits Viresh Kumar
2026-05-22 5:39 ` Zhongqiu Han
2026-05-22 4:19 ` [PATCH V2 3/3] cpufreq: conservative: Simplify frequency limit handling Viresh Kumar
2026-05-22 5:40 ` Zhongqiu Han
2026-05-22 16:43 ` [PATCH V2 0/3] cpufreq: Simplify freq " Rafael J. Wysocki
2026-05-25 15:49 ` 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=cover.1779423281.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stratosk@semaphore.gr \
--cc=sumit.semwal@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=zhenglifeng1@huawei.com \
--cc=zhongqiu.han@oss.qualcomm.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