From: Kevin Hilman <khilman@ti.com>
To: Dave Jones <davej@redhat.com>, cpufreq@vger.kernel.org
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] cpufreq: OMAP updates for v3.4
Date: Wed, 07 Mar 2012 12:20:41 -0800 [thread overview]
Message-ID: <87y5rci2na.fsf@ti.com> (raw)
Dave,
Please pull the following OMAP CPUfreq driver changes for v3.4.
Thanks,
Kevin
The following changes since commit b01543dfe67bb1d191998e90d20534dc354de059:
Linux 3.3-rc4 (2012-02-18 15:53:33 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/cpufreq
for you to fetch changes up to 42daffd2d6c665716d442d518022ecaad17ddf64:
cpufreq: OMAP: specify range for voltage scaling (2012-03-02 13:55:57 -0800)
----------------------------------------------------------------
Afzal Mohammed (1):
cpufreq: OMAP: specify range for voltage scaling
Kevin Hilman (1):
cpufreq: OMAP: scale voltage along with frequency
Russell King (1):
cpufreq: OMAP driver depends CPUfreq tables
drivers/cpufreq/Kconfig.arm | 5 +++
drivers/cpufreq/Makefile | 2 +-
drivers/cpufreq/omap-cpufreq.c | 72 +++++++++++++++++++++++++++++++++++++---
3 files changed, 73 insertions(+), 6 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] cpufreq: OMAP updates for v3.4
Date: Wed, 07 Mar 2012 12:20:41 -0800 [thread overview]
Message-ID: <87y5rci2na.fsf@ti.com> (raw)
Dave,
Please pull the following OMAP CPUfreq driver changes for v3.4.
Thanks,
Kevin
The following changes since commit b01543dfe67bb1d191998e90d20534dc354de059:
Linux 3.3-rc4 (2012-02-18 15:53:33 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/cpufreq
for you to fetch changes up to 42daffd2d6c665716d442d518022ecaad17ddf64:
cpufreq: OMAP: specify range for voltage scaling (2012-03-02 13:55:57 -0800)
----------------------------------------------------------------
Afzal Mohammed (1):
cpufreq: OMAP: specify range for voltage scaling
Kevin Hilman (1):
cpufreq: OMAP: scale voltage along with frequency
Russell King (1):
cpufreq: OMAP driver depends CPUfreq tables
drivers/cpufreq/Kconfig.arm | 5 +++
drivers/cpufreq/Makefile | 2 +-
drivers/cpufreq/omap-cpufreq.c | 72 +++++++++++++++++++++++++++++++++++++---
3 files changed, 73 insertions(+), 6 deletions(-)
next reply other threads:[~2012-03-07 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 20:20 Kevin Hilman [this message]
2012-03-07 20:20 ` [GIT PULL] cpufreq: OMAP updates for v3.4 Kevin Hilman
2012-03-07 20:30 ` Dave Jones
2012-03-07 20:30 ` Dave Jones
2012-03-15 17:00 ` Kevin Hilman
2012-03-15 17:00 ` Kevin Hilman
2012-03-14 16:41 ` Grazvydas Ignotas
2012-03-14 16:41 ` Grazvydas Ignotas
2012-03-14 16:44 ` Dave Jones
2012-03-14 16:44 ` Dave Jones
2012-03-14 17:22 ` Kevin Hilman
2012-03-14 17:22 ` Kevin Hilman
2012-03-14 17:38 ` Grazvydas Ignotas
2012-03-14 17:38 ` Grazvydas Ignotas
2012-03-15 14:25 ` Kevin Hilman
2012-03-15 14:25 ` Kevin Hilman
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=87y5rci2na.fsf@ti.com \
--to=khilman@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.