From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms
Date: Tue, 23 Jun 2015 14:00:55 +0530 [thread overview]
Message-ID: <20150623083055.GJ16776@linux> (raw)
In-Reply-To: <20150623082759.GF3245@x1>
On 23-06-15, 09:27, Lee Jones wrote:
> Okay, but the reasoning is the same. I consider the function to have
> failed, but the over-all failure culminates in just a warning that
> voltage scaling has indeed failed, but we can still go on with
> frequency scaling.
Ahh, I thought that the other opp-table will also have voltages.
> Unless his is a big blocker for you, I would like to keep these
> semantics.
No, the print is actually fine.
> So technically you are correct, but it makes the code slightly more
> confusing IMHO. Yes, it's one more line of code, but it's worth it to
> add clarity.
Your call :)
--
viresh
next prev parent reply other threads:[~2015-06-23 8:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:43 [PATCH 0/8] cpufreq: Introduce support for ST's cpufreq functionality Lee Jones
2015-06-22 15:43 ` [PATCH 1/8] ARM: STi: STiH407: Provide generic (safe) DVFS configuration Lee Jones
2015-06-22 15:43 ` [PATCH 2/8] ARM: STi: STiH407: Provide CPU with clocking information Lee Jones
2015-06-22 15:43 ` [PATCH 3/8] ARM: STi: STiH407: Link CPU with its voltage supply Lee Jones
2015-06-22 15:43 ` [PATCH 4/8] ARM: STi: STiH407: Provide a node for CPUFreq Lee Jones
2015-06-23 2:16 ` Viresh Kumar
2015-06-23 7:10 ` Lee Jones
2015-06-23 7:57 ` Viresh Kumar
2015-06-22 15:43 ` [PATCH 5/8] ARM: STi: STiH407: Move PWM nodes STiH407 => STiH407-family Lee Jones
2015-06-23 2:17 ` Viresh Kumar
2015-06-23 7:08 ` Lee Jones
2015-06-23 7:55 ` Viresh Kumar
2015-06-22 15:43 ` [PATCH 6/8] ARM: multi_v7_defconfig: Enable support for PWM Regulators Lee Jones
2015-06-22 15:43 ` [PATCH 7/8] cpufreq: st: Provide runtime initialised driver for ST's platforms Lee Jones
2015-06-23 2:50 ` Viresh Kumar
2015-06-23 7:16 ` Lee Jones
2015-06-23 7:31 ` [STLinux Kernel] " Maxime Coquelin
2015-06-23 8:03 ` Viresh Kumar
2015-06-23 8:27 ` Lee Jones
2015-06-23 8:30 ` Viresh Kumar [this message]
2015-06-23 9:00 ` Lee Jones
2015-06-23 8:00 ` Paul Bolle
2015-06-23 8:28 ` Lee Jones
2015-06-23 20:03 ` Paul Bolle
2015-06-24 7:33 ` Lee Jones
2015-06-22 15:43 ` [PATCH 8/8] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation Lee Jones
2015-06-23 2:34 ` Viresh Kumar
2015-06-23 7:06 ` Lee Jones
2015-06-23 7:55 ` Viresh Kumar
2015-06-23 8:38 ` Lee Jones
2015-06-23 8:52 ` Javier Martinez Canillas
2015-06-23 8:59 ` Lee Jones
2015-06-23 9:00 ` Viresh Kumar
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=20150623083055.GJ16776@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).