From: "zhenglifeng (A)" <zhenglifeng1@huawei.com>
To: <myungjoo.ham@samsung.com>, <kyungmin.park@samsung.com>,
<cw00.choi@samsung.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
<zhanjie9@hisilicon.com>, <lihuisong@huawei.com>,
<yubowen8@huawei.com>, <cenxinghai@h-partners.com>
Subject: Re: [PATCH 0/4] PM / devfreq: Some optimizations of devfreq
Date: Tue, 13 May 2025 20:52:39 +0800 [thread overview]
Message-ID: <a379625e-ece7-4b94-a482-014639624171@huawei.com> (raw)
In-Reply-To: <20250421030020.3108405-1-zhenglifeng1@huawei.com>
Gentle ping.
On 2025/4/21 11:00, Lifeng Zheng wrote:
>
> Lifeng Zheng (4):
> PM / devfreq: governor: Replace sscanf() with kstrtoul() in
> set_freq_store()
> PM / devfreq: Limit max_freq with scaling_min_freq
> PM / devfreq: Remove redundant devfreq_get_freq_range() calling in
> devfreq_add_device()
> PM / devfreq: Check governor before using governor->name
>
> drivers/devfreq/devfreq.c | 20 +++++---------------
> drivers/devfreq/governor_userspace.c | 6 +++++-
> 2 files changed, 10 insertions(+), 16 deletions(-)
>
prev parent reply other threads:[~2025-05-13 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 3:00 [PATCH 0/4] PM / devfreq: Some optimizations of devfreq Lifeng Zheng
2025-04-21 3:00 ` [PATCH 1/4] PM / devfreq: governor: Replace sscanf() with kstrtoul() in set_freq_store() Lifeng Zheng
2025-04-27 11:17 ` David Laight
2025-04-28 8:07 ` zhenglifeng (A)
2025-05-13 17:19 ` Chanwoo Choi
2025-04-21 3:00 ` [PATCH 2/4] PM / devfreq: Limit max_freq with scaling_min_freq Lifeng Zheng
2025-05-13 17:39 ` Chanwoo Choi
2025-04-21 3:00 ` [PATCH 3/4] PM / devfreq: Remove redundant devfreq_get_freq_range() calling in devfreq_add_device() Lifeng Zheng
2025-05-13 17:41 ` Chanwoo Choi
2025-04-21 3:00 ` [PATCH 4/4] PM / devfreq: Check governor before using governor->name Lifeng Zheng
2025-05-13 17:43 ` Chanwoo Choi
2025-05-13 12:52 ` zhenglifeng (A) [this message]
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=a379625e-ece7-4b94-a482-014639624171@huawei.com \
--to=zhenglifeng1@huawei.com \
--cc=cenxinghai@h-partners.com \
--cc=cw00.choi@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=kyungmin.park@samsung.com \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=myungjoo.ham@samsung.com \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.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 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.