From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: zhuguangqing83@gmail.com, viresh.kumar@linaro.org,
amit.kachhap@gmail.com, javi.merino@kernel.org,
rui.zhang@intel.com, amitk@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhuguangqing <zhuguangqing@xiaomi.com>,
"v5 . 4+" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] thermal/drivers/cpufreq_cooling: Update cpufreq_state only if state has changed
Date: Thu, 12 Nov 2020 12:24:05 +0100 [thread overview]
Message-ID: <55b484fb-1532-e130-3b05-5a7f5e18a536@linaro.org> (raw)
In-Reply-To: <20201106092243.15574-1-zhuguangqing83@gmail.com>
On 06/11/2020 10:22, zhuguangqing83@gmail.com wrote:
> From: Zhuguangqing <zhuguangqing@xiaomi.com>
>
> If state has not changed successfully and we updated cpufreq_state,
> next time when the new state is equal to cpufreq_state (not changed
> successfully last time), we will return directly and miss a
> freq_qos_update_request() that should have been.
>
> Fixes: 5130802ddbb1 ("thermal: cpu_cooling: Switch to QoS requests for freq limits")
> Cc: v5.4+ <stable@vger.kernel.org> # v5.4+
> Signed-off-by: Zhuguangqing <zhuguangqing@xiaomi.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Applied, thanks
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2020-11-12 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 9:22 [PATCH v2] thermal/drivers/cpufreq_cooling: Update cpufreq_state only if state has changed zhuguangqing83
2020-11-06 9:25 ` Viresh Kumar
2020-11-12 11:24 ` Daniel Lezcano [this message]
2020-11-24 9:36 ` [thermal: thermal/next] " thermal-bot for Zhuguangqing
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=55b484fb-1532-e130-3b05-5a7f5e18a536@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amit.kachhap@gmail.com \
--cc=amitk@kernel.org \
--cc=javi.merino@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=zhuguangqing83@gmail.com \
--cc=zhuguangqing@xiaomi.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;
as well as URLs for NNTP newsgroup(s).