All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: new PM branch: OPP layer included
Date: Fri, 23 Apr 2010 16:23:59 -0700	[thread overview]
Message-ID: <87hbn1u50w.fsf@deeprootsystems.com> (raw)

Hello,

I just pushed a new PM branch.  I did a bunch of reordering and
restructuring of branches to include the OPP layer (more on this
below.)


OPP layer: 

pm-wip-opp branch gone, merged into PM branch

What was in pm-wip-opp has now been broken up into a set of patches
that can be combined and queued for upstream (pm-opp branch) as well
as sets of patches for SR and SRF which are now on their respective
branches (pm-sr, pm-srf)

Next step is to combine the patches in pm-opp branch into a sensible
series that can be submitted for the next merge window.


Smart Reflex:

Thara's v3 series available as pm-wip-sr.  This is now based directly
on the new PM branch instead of on pm-wip-opp.

NOTE: the hwmod patches are now merged into l-o (omap-fixes branch)
      so they are no longer in pm-wip-sr.

I didn't get to reviewing this series yet, but did test it out a bit
on top of thenew PM branch.  I gave this some basic testing on n900
and Zoom3 (required a u-boot update first) but basic OPP changes from
userspace governor worked on both.

  
SRF:

This is still included in the PM branch (pm-srf branch), but will be
removed from the official PM branch.  It will be maintained as a
separate branch for a short time (1 month max) and then dropped.
Anyone else who wants to continue maintenance of SRF is free to do so.


Kevin

             reply	other threads:[~2010-04-23 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 23:23 Kevin Hilman [this message]
2010-04-26 12:57 ` new PM branch: OPP layer included G, Manjunath Kondaiah
2010-04-26 16:51   ` Kevin Hilman
2010-05-04 17:43 ` Kevin Hilman

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=87hbn1u50w.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.