public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>
Cc: Russell King <linux@arm.linux.org.uk>
Subject: Clock and domain patches pushed to l-o, queue to be prepared for RMK
Date: Mon, 22 Sep 2008 18:05:34 +0300	[thread overview]
Message-ID: <20080922150532.GB8171@atomide.com> (raw)

Hi all,

I've pushed a pile of patches from Paul to l-o tree:

[PATCH v2 0/7] OMAP2/3 clock: revise DPLL bypass handling in clock tree
[PATCH v2 00/11] OMAP2/3 clock: encode prcm_mod for each struct clk
[PATCH 0/5] OMAP2/3 clock: revise module idlest handling

Paul, could you please take all the pending clock and domain
patches and post them to LAKML so we can queue them for Russell?

You should be able to compress some add-fix-fix cycles out of them
into just add cycles :)

I'll leave out all the clock and domain patches from the pending
omap2-upstream series so they're independent patch sets. I'll post a
refreshed omap2-upstream at some point soonish to LAKML.

Regards,

Tony

                 reply	other threads:[~2008-09-22 15:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080922150532.GB8171@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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