public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 0/3] omap2 clock: create clock24xx.[ch] in preparation for 3430 clock code
Date: Mon, 17 Sep 2007 11:16:06 -0700	[thread overview]
Message-ID: <20070917181605.GC21226@atomide.com> (raw)
In-Reply-To: <20070912060141.645853958@pwsan.com>

* Paul Walmsley <paul@pwsan.com> [070912 01:40]:
> Hello,
> 
> this short patch series separates OMAP24xx clock definitions and code
> from common clock code and headers.  It's in preparation for OMAP3430
> clock definitions and code.
> 
> All this happens in patches 2 and 3 of this series.  The remaining
> patch 1 moves some SDRC-related defines from clock.h into sdrc.h where
> they belong.
> 
> The diffstat looks big, but the patches are mostly just cut and paste,
> with a few minor changes to expose common functions to the linker, and
> to satisfy checkpatch (at least somewhat).
> 
> Review and comments are appreciated, as always.

Pushing this series today.

Tony

      parent reply	other threads:[~2007-09-17 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  6:01 [PATCH 0/3] omap2 clock: create clock24xx.[ch] in preparation for 3430 clock code Paul Walmsley
2007-09-12  6:01 ` [PATCH 1/3] omap2 clock: move SDRC autorefresh counter defines into sdrc.h Paul Walmsley
2007-09-12  6:01 ` [PATCH 2/3] omap2 clock: move 24xx clock definitions from clock.h into clock24xx.h Paul Walmsley
2007-09-12  6:01 ` [PATCH 3/3] omap2 clock: move 24xx-specific clock code from clock.c into clock24xx.c Paul Walmsley
2007-09-17 18:16 ` 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=20070917181605.GC21226@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