linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Shilimkar, Santosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
Date: Fri, 20 Jul 2012 12:06:50 +0530	[thread overview]
Message-ID: <CAMQu2gz3XXQdG3T=jSboZ8cW-gKO33k7+OUPaQpjpUcnitk_RA@mail.gmail.com> (raw)
In-Reply-To: <1342713281-31114-2-git-send-email-shawn.guo@linaro.org>

On Thu, Jul 19, 2012 at 9:24 PM, Shawn Guo <shawn.guo@linaro.org> wrote:
>
> From: Richard Zhao <richard.zhao@linaro.org>
>
> If CONFIG_SMP, cpufreq skips loops_per_jiffy update, because different
> arch has different per-cpu loops_per_jiffy definition.
>
> Signed-off-by: Richard Zhao <richard.zhao@linaro.org>
> Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
Nice. Avoids other driver duplicating this code.
May be you can keep Richard's credit in commit too.

FWIW, Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>

  reply	other threads:[~2012-07-20  6:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 15:54 [PATCH 0/3] Add a generic cpufreq-cpu0 driver Shawn Guo
2012-07-19 15:54 ` [PATCH 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Shawn Guo
2012-07-20  6:36   ` Shilimkar, Santosh [this message]
2012-07-20  7:56     ` Shawn Guo
2012-07-20  8:27       ` Shilimkar, Santosh
2012-07-19 15:54 ` [PATCH 2/3] PM / OPP: Initialize OPP table from device tree Shawn Guo
2012-07-20  6:00   ` Menon, Nishanth
2012-07-20  8:46     ` Shawn Guo
2012-07-20  9:04       ` Menon, Nishanth
2012-07-19 15:54 ` [PATCH 3/3] cpufreq: Add a generic cpufreq-cpu0 driver Shawn Guo
2012-07-20  6:52   ` Shilimkar, Santosh
2012-07-20 12:33     ` Shawn Guo
2012-07-20 15:50       ` Turquette, Mike
2012-07-21  5:04         ` Shilimkar, Santosh
2012-07-21  6:38           ` Shawn Guo
2012-07-27  2:04             ` Richard Zhao
2012-07-30  4:57               ` Shawn Guo
2012-07-20 12:51   ` Richard Zhao
2012-07-20 13:15     ` Shawn Guo
2012-07-26 13:11   ` Mark Brown
2012-07-27  2:13     ` Richard Zhao
2012-07-27 10:08       ` Mark Brown
2012-07-30  6:52     ` Shawn Guo
2012-07-30  8:20       ` Shawn Guo
2012-07-30 18:55         ` Mark Brown
2012-07-30 18:53       ` Mark Brown
2012-07-31  4:20         ` Shawn Guo
2012-07-31 13:40           ` Mark Brown
2012-07-27  6:33   ` Richard Zhao
2012-07-30  8:17     ` Shawn Guo
2012-07-30  8:50       ` Richard Zhao
2012-07-30  9:24         ` Shawn Guo
2012-07-19 18:39 ` [PATCH 0/3] " Rafael J. Wysocki
2012-07-20  0:29   ` Shawn Guo

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='CAMQu2gz3XXQdG3T=jSboZ8cW-gKO33k7+OUPaQpjpUcnitk_RA@mail.gmail.com' \
    --to=santosh.shilimkar@ti.com \
    --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).