From: Kevin Hilman <khilman@deeprootsystems.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, rnayak@ti.com, b-cousson@ti.com
Subject: Re: [PATCH 0/3 v2] omap: pm: Move the common code to allow re-use
Date: Tue, 14 Sep 2010 13:29:52 -0700 [thread overview]
Message-ID: <878w34m5kv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1284492841-14858-1-git-send-email-santosh.shilimkar@ti.com> (Santosh Shilimkar's message of "Wed, 15 Sep 2010 01:03:58 +0530")
Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
> (v2 is rebased on Kevin's 'pm-next' branch)
>
> This is small series moves some common pm code out of pm34xx.c so
> that omap4 can re-use this and not duplicate it.
>
> It's boot tested on OMAP3/4 with omap3_defconfig and also simple
> test with millisecond debugfs entry and suspend/resume.
>
> Santosh Shilimkar (3):
> omap: pm-debug: Move common debug code to pm-debug.c
> omap: pm-debug: Enable wakeup_timer_milliseconds debugfs entry
> omap: pm: Move set_pwrdm_state routine to common pm.c
Thanks, adding to my pm-next queue for 2.6.37.
Kevin
prev parent reply other threads:[~2010-09-14 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 19:33 [PATCH 0/3 v2] omap: pm: Move the common code to allow re-use Santosh Shilimkar
2010-09-14 19:33 ` [PATCH 1/3 v2] omap: pm-debug: Move common debug code to pm-debug.c Santosh Shilimkar
2010-09-14 19:34 ` [PATCH 2/3 v2] omap: pm-debug: Enable wakeup_timer_milliseconds debugfs entry Santosh Shilimkar
2010-09-14 19:34 ` [PATCH 3/3 v2] omap: pm: Move set_pwrdm_state routine to common pm.c Santosh Shilimkar
2010-09-14 20:30 ` [PATCH 1/3 v2] omap: pm-debug: Move common debug code to pm-debug.c Kevin Hilman
2010-09-14 20:29 ` Kevin Hilman [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=878w34m5kv.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@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 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.