public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs
Date: Wed, 16 Dec 2009 11:59:04 -0800	[thread overview]
Message-ID: <87pr6eadx3.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1260594031-17268-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Fri\, 11 Dec 2009 23\:00\:28 -0600")

Nishanth Menon <nm@ti.com> writes:

> Hi,
> Thanks for all the comments. Here are the *changed* patches since V5
>
> What changed in V5:
> * review comment incorporated
> * vsel is deprecated now
> * I seem to have hit a checkpatch.pl bug as in 
>   http://lkml.org/lkml/2009/12/11/573, made me check the usage
>   of __deprecated for struct params, and used it in a
>   consistent manner to functions..
> * More warnings added to build :( (deprecated ones ofcourse)
> * removed OMAP_OPP_DEF_TERMINATOR
> * 3430 and 3630 patches changed as a result
>
> History:
> V4: http://marc.info/?t=126033962600001&r=1&w=2
> V3: http://marc.info/?t=125912234200001&r=1&w=2
> V2: http://marc.info/?l=linux-omap&m=125809232732700&w=2
> V1: http://marc.info/?l=linux-omap&m=125800488923479&w=2
>
> Ref: http://elinux.org/OMAP_Power_Management#Future_directions
>
> TODO: The list is still the same as in:
> http://marc.info/?l=linux-omap&m=126033945313269&w=2

FYI...

To facilitate the ongoing discussions on OPP rework, and to have a
common base, this series is available as a branch in my linux-omap-pm
repo[1].

The branch is called 'pm-wip-opp' and I have rebased onto the PM
branch I pushed today.

Kevin

[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git

  parent reply	other threads:[~2009-12-16 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH 02/10 V4] omap3: pm: introduce opp accessor functions>
2009-12-12  5:00 ` [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs Nishanth Menon
2009-12-12  5:00   ` [PATCH 02/10 V5] omap3: pm: introduce opp accessor functions Nishanth Menon
2009-12-12  5:00     ` [PATCH 03/10 V5] omap3: pm: use opp accessor functions for omap34xx Nishanth Menon
2009-12-12  5:00       ` [PATCH 09/10 V5] omap3: pm: introduce 3630 opps Nishanth Menon
2009-12-16 19:59   ` Kevin Hilman [this message]
2009-12-16 22:37     ` [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs Kevin Hilman
2009-12-17  3:22       ` Menon, Nishanth
2009-12-17 16:10         ` Kevin Hilman
2009-12-18 10:26           ` Romit Dasgupta
2009-12-18 16:04             ` 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=87pr6eadx3.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.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