From: Tony Lindgren <tony@atomide.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael Wysocki" <rjw@rjwysocki.net>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-pm@vger.kernel.org,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Eduardo Valentin" <edubezval@gmail.com>,
"Zhang Rui" <rui.zhang@intel.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
daniel.lezcano@linaro.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/10] ARM: dts: omap: Remove "cooling-{min|max}-level" for CPU nodes
Date: Mon, 12 Feb 2018 09:17:09 -0800 [thread overview]
Message-ID: <20180212171709.GB6364@atomide.com> (raw)
In-Reply-To: <65c21dd1f5299d624ddb0b5e607226d86f745e19.1518166039.git.viresh.kumar@linaro.org>
* Viresh Kumar <viresh.kumar@linaro.org> [180209 00:59]:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of the kernel currently and the max cooling state of
> a CPU cooling device is found by referring to the cpufreq table instead.
>
> Remove the unused properties from the CPU nodes.
It seem this patch needs to wait before we can apply, right?
Regards,
Tony
next prev parent reply other threads:[~2018-02-12 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 8:58 [PATCH 00/10] thermal: Remove "cooling-{min|max}-level" properties Viresh Kumar
2018-02-09 8:58 ` [PATCH 02/10] ARM: dts: omap: Remove "cooling-{min|max}-level" for CPU nodes Viresh Kumar
2018-02-12 17:17 ` Tony Lindgren [this message]
2018-02-12 17:18 ` Tony Lindgren
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=20180212171709.GB6364@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).