From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Richard Zhao <richard.zhao@freescale.com>
Subject: Re: [PATCH] cpufreq: OMAP: remove loops_per_jiffy recalculate for smp
Date: Fri, 14 Sep 2012 07:21:51 -0700 [thread overview]
Message-ID: <87sjak8z28.fsf@deeprootsystems.com> (raw)
In-Reply-To: <201209072115.08252.rjw@sisk.pl> (Rafael J. Wysocki's message of "Fri, 7 Sep 2012 21:15:08 +0200")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Friday, September 07, 2012, Shawn Guo wrote:
>> From: Richard Zhao <richard.zhao@freescale.com>
>>
>> With ARM smp common code recalculating loops_per_jiffy in a cpufreq
>> transiton notifier call, the loops_per_jiffy recalculate in omap-cpufreq
>> driver becomes redundant. Remove it.
>>
>> Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
>> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
>
> I suppose that Kevin is going to handle this, right?
Normally, yes, but I'm a bit behind, still catching up from some time
off.
> Kevin, if you want me to pull new material for v3.7, it's about time to get
> it ready.
Rafael, feel free to add this one to your pm-cpufreq branch with
Acked-by: Kevin Hilman <khilman@ti.com>
Also, we have one other OMAP CPUfreq change that needs to go via the
OMAP tree with some corresponding clock changes:
http://marc.info/?l=linux-omap&m=134740995111966&w=2
Can you ack that one?
Thanks,
Kevin
next prev parent reply other threads:[~2012-09-14 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 1:23 [PATCH] cpufreq: OMAP: remove loops_per_jiffy recalculate for smp Shawn Guo
2012-09-07 19:15 ` Rafael J. Wysocki
2012-09-14 14:21 ` Kevin Hilman [this message]
2012-09-14 19:01 ` 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=87sjak8z28.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=richard.zhao@freescale.com \
--cc=rjw@sisk.pl \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@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