From: Eduardo Valentin <edubezval@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Javi Merino <javi.merino@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Lukasz Luba <llu.ker.dev@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Punit Agrawal <punit.agrawal@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Zhang Rui <rui.zhang@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Linux PM <linux-pm@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] cpu_cooling: Drop static-power related stuff
Date: Wed, 22 Nov 2017 07:38:05 -0800 [thread overview]
Message-ID: <20171122153804.GB24699@localhost.localdomain> (raw)
In-Reply-To: <20171122111013.GB4084@vireshk-i7>
On Wed, Nov 22, 2017 at 04:40:13PM +0530, Viresh Kumar wrote:
> On 22-11-17, 10:59, Sudeep Holla wrote:
> > IMO, if the $subject code is expected to be used on Juno, then my answer
> > is no if one can't test it reliably and also prove that static power
> > really matters on Juno. So far, I have heard both the above is not
> > possible. So please delete the code if Juno is the only user in
> > short and mid term. We can get the code back if we find any users in
> > longer term.
>
> Its funny that the $subject patch receives few Acks and Nacks every day now :)
I am still in favor to removed it, my ack still sustains,
as my original motivation to keep this is pointless as people responsible
for the code is not willing upstream it nor have the time nor will get
further vendors to use it.
>
> --
> viresh
next prev parent reply other threads:[~2017-11-22 15:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 9:19 [PATCH 0/4] cpu_cooling: cooling dev registration cleanups Viresh Kumar
2017-11-15 9:19 ` [PATCH 1/4] cpu_cooling: Make of_cpufreq_power_cooling_register() parse DT Viresh Kumar
2017-11-15 9:19 ` [PATCH 2/4] cpu_cooling: Remove unused cpufreq_power_cooling_register() Viresh Kumar
2017-11-15 9:19 ` [PATCH 3/4] cpu_cooling: Keep only one of_cpufreq*cooling_register() helper Viresh Kumar
2017-11-15 9:19 ` [PATCH 4/4] cpu_cooling: Drop static-power related stuff Viresh Kumar
2017-11-15 10:18 ` Daniel Lezcano
2017-11-15 11:25 ` Viresh Kumar
2017-11-15 15:43 ` Eduardo Valentin
2017-11-15 18:17 ` Rafael J. Wysocki
2017-11-15 18:20 ` Eduardo Valentin
2017-11-16 15:02 ` Ionela Voinescu
2017-11-16 15:20 ` Viresh Kumar
2017-11-16 23:31 ` Rafael J. Wysocki
2017-11-16 23:44 ` Eduardo Valentin
2017-11-17 11:02 ` Punit Agrawal
2017-11-17 11:06 ` Viresh Kumar
2017-11-21 11:30 ` Ionela Voinescu
2017-11-21 13:06 ` Daniel Lezcano
2017-11-21 15:56 ` Lukasz Luba
2017-11-21 16:08 ` Vincent Guittot
2017-11-21 16:57 ` Eduardo Valentin
2017-11-21 18:00 ` Javi Merino
2017-11-21 18:05 ` Daniel Lezcano
2017-11-21 18:13 ` Eduardo Valentin
2017-11-21 23:32 ` Lukasz Luba
2017-11-21 18:12 ` Eduardo Valentin
2017-11-22 10:59 ` Sudeep Holla
2017-11-22 11:10 ` Viresh Kumar
2017-11-22 11:17 ` Sudeep Holla
2017-11-22 15:38 ` Eduardo Valentin [this message]
2017-11-22 15:34 ` Eduardo Valentin
2017-11-22 16:04 ` Sudeep Holla
2017-11-22 1:25 ` Viresh Kumar
2017-11-22 11:08 ` Viresh Kumar
2017-11-21 17:03 ` Lukasz Luba
2017-11-21 17:09 ` Eduardo Valentin
2017-11-21 17:49 ` Daniel Lezcano
2017-11-16 2:47 ` Viresh Kumar
2017-11-17 7:55 ` Daniel Lezcano
2017-11-15 11:31 ` Javi Merino
2017-11-15 11:39 ` Daniel Lezcano
2017-11-15 15:09 ` Eduardo Valentin
2017-11-15 18:08 ` [PATCH 0/4] cpu_cooling: cooling dev registration cleanups 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=20171122153804.GB24699@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=amit.kachhap@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=ionela.voinescu@arm.com \
--cc=javi.merino@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llu.ker.dev@gmail.com \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=rui.zhang@intel.com \
--cc=sudeep.holla@arm.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