From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC CPUFreq Updates for v3.17
Date: Sat, 12 Jul 2014 15:53:15 +0200 [thread overview]
Message-ID: <cover.1405172884.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these second round of Renesas ARM based SoC CPUFreq
updates for v3.17.
This pull request is based on the previous round of
such requests, tagged as renesas-cpufreq-for-v3.17,
which I have already sent a pull-request for.
The following changes since commit 06e32c91dbce3c24ccbe84e3af2a35199662bca0:
ARM: shmobile: add cpufreq-cpu0 driver for common SH-Mobile (2014-06-16 19:50:54 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git renesas-cpufreq2-for-v3.17
for you to fetch changes up to e423d12cbcb9576785e891617888f627f1f57bf4:
ARM: shmobile: Remove opps table check for cpufreq (2014-07-09 10:48:58 +0200)
----------------------------------------------------------------
Second Round of Renesas ARM Based SoC CPUFreq Updates for v3.17
* Remove opps table check for cpufreq as this is already handled
by the driver
----------------------------------------------------------------
Gaku Inami (1):
ARM: shmobile: Remove opps table check for cpufreq
arch/arm/mach-shmobile/cpufreq.c | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
next reply other threads:[~2014-07-12 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 13:53 Simon Horman [this message]
2014-07-12 13:53 ` [PATCH] ARM: shmobile: Remove opps table check for cpufreq Simon Horman
2014-07-13 4:47 ` [GIT PULL] Second Round of Renesas ARM Based SoC CPUFreq Updates for v3.17 Olof Johansson
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=cover.1405172884.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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).