From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 0/7] OMAP3 clock patches: first set (take two)
Date: Fri, 28 Sep 2007 16:14:22 -0700 [thread overview]
Message-ID: <20070928231421.GW10076@atomide.com> (raw)
In-Reply-To: <20070927061119.551228401@pwsan.com>
* Paul Walmsley <paul@pwsan.com> [070926 23:16]:
> Hello,
>
> this is take two of the initial OMAP3430 clock tree patches, with
> several bug fixes. UART clock enable warnings are now fixed,
> and some clocks that didn't recalculate rates correctly are now
> fixed. A few more details are in the per-patch notes.
>
> Boot tested on N800 and 3430SDP. Diffstat and size have been updated at
> the end of the message. Testing welcome, as always.
Great, I've pushed this series.
Tony
prev parent reply other threads:[~2007-09-28 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 6:11 [PATCH 0/7] OMAP3 clock patches: first set (take two) Paul Walmsley
2007-09-27 6:11 ` [PATCH 1/7] omap2 arch: fix CONTROL_DEVCONF addresses for OMAP3430 Paul Walmsley
2007-09-27 6:11 ` [PATCH 2/7] omap2 clock: split out OMAP2/3 common defines, clksel rates Paul Walmsley
2007-09-27 6:11 ` [PATCH 3/7] omap2 clock: add support for inverted enable bits Paul Walmsley
2007-09-27 6:11 ` [PATCH 4/7] omap2 clock: add OMAP3430 clock definitions, basic code Paul Walmsley
2007-09-27 6:11 ` [PATCH 5/7] gpmc: fix GPMC code to boot on 3430 Paul Walmsley
2007-09-27 6:11 ` [PATCH 6/7] dmtimer: fix source clocks for 3430 Paul Walmsley
2007-09-27 6:11 ` [PATCH 7/7] gpio: fix GPIO clock code " Paul Walmsley
2007-09-28 23:14 ` 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=20070928231421.GW10076@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--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