From: Stephen Warren <swarren@wwwdotorg.org>
To: Joseph Lo <josephl@nvidia.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: tegra: fix the wrong clock name
Date: Fri, 23 Aug 2013 10:24:39 -0600 [thread overview]
Message-ID: <52178CC7.2070003@wwwdotorg.org> (raw)
In-Reply-To: <1377222238-9439-1-git-send-email-josephl@nvidia.com>
On 08/22/2013 07:43 PM, Joseph Lo wrote:
> The "cpu" and "pclk_p_cclk" was a virtual clock name that was used in
> the legacy Tegra clock framework. It was not used after converting to
> CCF. Fix it as the correct clock name that we are using.
Tested-by: Stephen Warren <swarren@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: tegra: fix the wrong clock name
Date: Fri, 23 Aug 2013 10:24:39 -0600 [thread overview]
Message-ID: <52178CC7.2070003@wwwdotorg.org> (raw)
In-Reply-To: <1377222238-9439-1-git-send-email-josephl@nvidia.com>
On 08/22/2013 07:43 PM, Joseph Lo wrote:
> The "cpu" and "pclk_p_cclk" was a virtual clock name that was used in
> the legacy Tegra clock framework. It was not used after converting to
> CCF. Fix it as the correct clock name that we are using.
Tested-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-08-23 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 1:43 [PATCH] cpufreq: tegra: fix the wrong clock name Joseph Lo
2013-08-23 1:43 ` Joseph Lo
[not found] ` <1377222238-9439-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-23 4:53 ` Viresh Kumar
2013-08-23 4:53 ` Viresh Kumar
2013-08-23 16:24 ` Stephen Warren [this message]
2013-08-23 16:24 ` Stephen Warren
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=52178CC7.2070003@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=cpufreq@vger.kernel.org \
--cc=josephl@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.