From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] OMAP clock/OPP/SDRC fixes for 2.6.33-rc
Date: Wed, 06 Jan 2010 13:44:15 -0700 [thread overview]
Message-ID: <20100106204346.15002.89343.stgit@localhost.localdomain> (raw)
Hello,
This series contains OMAP clock/OPP/SDRC fixes for 2.6.33-rc. It
applies against the last set of fixes sent to Tony, which in turn
applies against 2.6.33-rc3.
The most important patch here is Cory's OMAP1 clock fix; the
others are relatively minor.
- Paul
---
Cory Maccarrone (1):
OMAP1 clock: remove __initdata from struct clk_functions to prevent crash
Felipe Balbi (1):
OMAP2xxx clock: clk2xxx.c doesn't compile if CPUFREQ is enabled
Paul Walmsley (3):
OMAP2xxx OPP: clean up comments in OPP data
OMAP2 clock: dynamically allocate CPUFreq frequency table
OMAP clock/CPUFreq: avoid leaking the CPUFreq frequency table
arch/arm/mach-omap1/clock_data.c | 2 +
arch/arm/mach-omap2/clock2xxx.c | 57 ++++++++++++++++++++++++++-----
arch/arm/mach-omap2/opp2420_data.c | 38 +++++++++++----------
arch/arm/mach-omap2/opp2430_data.c | 30 ++++++++--------
arch/arm/plat-omap/clock.c | 10 +++++
arch/arm/plat-omap/cpu-omap.c | 1 +
arch/arm/plat-omap/include/plat/clock.h | 2 +
7 files changed, 97 insertions(+), 43 deletions(-)
next reply other threads:[~2010-01-06 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 20:44 Paul Walmsley [this message]
2010-01-06 20:44 ` [PATCH 1/5] OMAP1 clock: remove __initdata from struct clk_functions to prevent crash Paul Walmsley
2010-01-06 20:44 ` [PATCH 2/5] OMAP2xxx clock: clk2xxx.c doesn't compile if CPUFREQ is enabled Paul Walmsley
2010-01-06 20:44 ` [PATCH 3/5] OMAP2xxx OPP: clean up comments in OPP data Paul Walmsley
2010-01-06 20:44 ` [PATCH 4/5] OMAP2 clock: dynamically allocate CPUFreq frequency table Paul Walmsley
2010-01-06 20:44 ` [PATCH 5/5] OMAP clock/CPUFreq: avoid leaking the " Paul Walmsley
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=20100106204346.15002.89343.stgit@localhost.localdomain \
--to=paul@pwsan.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).