From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] change lpj in arm smp common code
Date: Wed, 29 Feb 2012 15:18:13 +0800 [thread overview]
Message-ID: <1330499895-12364-1-git-send-email-richard.zhao@linaro.org> (raw)
The two patches were originally in [PATCH V6 0/7] add a generic cpufreq driver.
I seperated them and hope they can go to upstream earlier.
Richard Zhao (2):
ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp
cpufreq: OMAP: remove loops_per_jiffy recalculate for smp
arch/arm/kernel/smp.c | 54 ++++++++++++++++++++++++++++++++++++++++
drivers/cpufreq/omap-cpufreq.c | 36 --------------------------
2 files changed, 54 insertions(+), 36 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-02-29 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 7:18 Richard Zhao [this message]
2012-02-29 7:18 ` [PATCH 1/2] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2012-02-29 8:42 ` Shilimkar, Santosh
2012-02-29 7:18 ` [PATCH 2/2] cpufreq: OMAP: remove loops_per_jiffy recalculate " Richard Zhao
2012-02-29 8:42 ` Shilimkar, Santosh
2012-02-29 18:21 ` [PATCH 0/2] change lpj in arm smp common code Kevin Hilman
2012-04-01 1:20 ` Richard Zhao
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=1330499895-12364-1-git-send-email-richard.zhao@linaro.org \
--to=richard.zhao@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).