From: Lukasz Luba <lukasz.luba@arm.com>
To: daniel.lezcano@linaro.org
Cc: amitk@kernel.org, rui.zhang@intel.com, viresh.kumar@linaro.org,
rafael@kernel.org, dietmar.eggemann@arm.com, rostedt@goodmis.org,
mingo@redhat.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Thermal cpufreq & devfreq cooling minor clean-ups
Date: Tue, 14 Jun 2022 13:51:35 +0100 [thread overview]
Message-ID: <92f56aed-e6cd-c65b-f42f-5bd1e07b90c5@arm.com> (raw)
In-Reply-To: <20220613124327.30766-1-lukasz.luba@arm.com>
Hi Daniel,
On 6/13/22 13:43, Lukasz Luba wrote:
> Hi all,
>
> This is v2 of some minor clean-ups for the thermal cpufreq and devfreq
> cooling code.
>
> Changes:
> v2:
> - extened the cpufreq_cooling_device with private ops field, to not waste
> memory and simplify allocation/free code (Viresh)
> - added devfreq_cooling clean-up to align with cpufreq cooling code
> - added ACKs from Viresh for patch 2/4 and path 3/4
> - added missing maintainers of tracing to CC list
>
> Regards,
> Lukasz
>
> Lukasz Luba (4):
> thermal: cpufreq_cooling: Use private callback ops for each cooling
> device
> thermal: cpufreq_cooling : Refactor thermal_power_cpu_get_power
> tracing
> thermal: cpufreq_cooling: Update outdated comments
> thermal: devfreq_cooling: Extend the devfreq_cooling_device with ops
>
> drivers/thermal/cpufreq_cooling.c | 77 ++++++++++---------------------
> drivers/thermal/devfreq_cooling.c | 27 ++++-------
> include/trace/events/thermal.h | 28 ++++-------
> 3 files changed, 42 insertions(+), 90 deletions(-)
>
Could you have a look and take the patches into your tree, please?
The 3 of 4 patches got ACKs, the last one is devfreq cooling, which
is pretty minor change.
Regards,
Lukasz
next prev parent reply other threads:[~2022-06-14 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:43 Lukasz Luba
2022-06-13 12:43 ` [PATCH v2 1/4] thermal: cpufreq_cooling: Use private callback ops for each cooling device Lukasz Luba
2022-06-14 2:24 ` Viresh Kumar
2022-06-14 9:50 ` Lukasz Luba
2022-06-13 12:43 ` [PATCH v2 2/4] thermal: cpufreq_cooling : Refactor thermal_power_cpu_get_power tracing Lukasz Luba
2022-06-13 12:43 ` [PATCH v2 3/4] thermal: cpufreq_cooling: Update outdated comments Lukasz Luba
2022-06-13 12:43 ` [PATCH v2 4/4] thermal: devfreq_cooling: Extend the devfreq_cooling_device with ops Lukasz Luba
2022-06-14 12:51 ` Lukasz Luba [this message]
2022-06-14 18:26 ` [PATCH v2 0/4] Thermal cpufreq & devfreq cooling minor clean-ups Daniel Lezcano
2022-06-15 7:47 ` Lukasz Luba
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=92f56aed-e6cd-c65b-f42f-5bd1e07b90c5@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--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
all inboxes | Powered by JetHome®