From: Shawn Guo <shawn.guo@freescale.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Anson Huang <b20788@freescale.com>
Cc: viresh.kumar@linaro.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH V2] cpufreq: imx6: remove pu regulator dependency for SOCs with no PU regulator
Date: Fri, 18 Jul 2014 16:31:18 +0800 [thread overview]
Message-ID: <20140718083116.GD8537@dragon> (raw)
In-Reply-To: <1403250138-25030-1-git-send-email-b20788@freescale.com>
On Fri, Jun 20, 2014 at 03:42:18PM +0800, Anson Huang wrote:
> PU regulator is not a necessary regulator for cpufreq, not all
> i.MX6 SoCs have PU regulator, only if SOC has PU regulator, then its
> voltage must be equal to SOC regulator, so remove the dependency
> to support i.MX6SX which has no PU regulator.
>
> Signed-off-by: Anson Huang <b20788@freescale.com>
Rafael,
Can you please apply this for 3.17? Thanks.
Shawn
next prev parent reply other threads:[~2014-07-18 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 7:42 [PATCH V2] cpufreq: imx6: remove pu regulator dependency for SOCs with no PU regulator Anson Huang
2014-06-20 8:30 ` Viresh Kumar
2014-06-21 12:28 ` Shawn Guo
2014-07-18 8:31 ` Shawn Guo [this message]
2014-07-19 0:06 ` 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=20140718083116.GD8537@dragon \
--to=shawn.guo@freescale.com \
--cc=b20788@freescale.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).