From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 0/4] OMAP2xxx clock/CPUFreq: fix compilation errors; clean up
Date: Tue, 5 Jan 2010 10:28:56 -0800 [thread overview]
Message-ID: <20100105182856.GF12378@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1001051121140.2083@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [100105 10:20]:
> On Tue, 5 Jan 2010, Tony Lindgren wrote:
>
> > * Paul Walmsley <paul@pwsan.com> [100105 09:35]:
> > > Hello,
> > >
> > > This series fixes several compilation errors for OMAP2xxx chips when
> > > CONFIG_CPU_FREQ is set. These were reported and partially fixed
> > > by Felipe Balbi <felipe.balbi@nokia.com>.
> > >
> > > Considerable work is still needed to fully support dynamic frequency
> > > changes on OMAP2xxx-series chips. Readers interested in such a
> > > project are encouraged to review the Maemo Diablo RX-34 and RX-44
> > > kernel source at:
> > >
> > > http://repository.maemo.org/pool/diablo/free/k/kernel-source-diablo/
> > >
> > > Boot-tested on N800 with n8x0_defconfig with CONFIG_CPU_FREQ; compile-tested
> > > for 2430SDP.
> > >
> > > This second version also incorporates some comments from Felipe.
> >
> > These look good to me, can you please send them one more time with
> > LAKML Cc'd for a quick review there?
>
> Yes, I plan to send them there along with some other queued fixes for
> another .33-rc fixes series.
OK, thanks.
Tony
prev parent reply other threads:[~2010-01-05 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 17:35 [PATCH v2 0/4] OMAP2xxx clock/CPUFreq: fix compilation errors; clean up Paul Walmsley
2010-01-05 17:35 ` [PATCH v2 1/4] OMAP2xxx clock: clk2xxx.c doesn't compile if CPUFREQ is enabled Paul Walmsley
2010-01-05 17:35 ` [PATCH v2 2/4] OMAP2xxx OPP: clean up comments in OPP data Paul Walmsley
2010-01-05 17:35 ` [PATCH v2 3/4] OMAP2 clock: dynamically allocate CPUFreq frequency table Paul Walmsley
2010-01-05 17:35 ` [PATCH v2 4/4] OMAP clock/CPUFreq: avoid leaking the " Paul Walmsley
2010-01-07 0:06 ` Kevin Hilman
2010-01-07 0:54 ` Paul Walmsley
2010-01-05 18:06 ` [PATCH v2 0/4] OMAP2xxx clock/CPUFreq: fix compilation errors; clean up Tony Lindgren
2010-01-05 18:22 ` Paul Walmsley
2010-01-05 18:28 ` Tony Lindgren [this message]
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=20100105182856.GF12378@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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