From: Kevin Hilman <khilman@deeprootsystems.com>
To: Lesly A M <leslyam@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v4 0/5] omap3: pm: Update TRITON power scripts and making it generic
Date: Tue, 06 Apr 2010 14:23:07 -0700 [thread overview]
Message-ID: <877hoknumc.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1270030752-1900-1-git-send-email-leslyam@ti.com> (Lesly A. M.'s message of "Wed\, 31 Mar 2010 15\:49\:12 +0530")
Lesly A M <leslyam@ti.com> writes:
> This series of patch implements a updated TRITON power scripts.
> Also moving the sleep, wakeup & warm_reset sequence to a generic script file,
> which can be used by different OMAP3 board with the power companion chip TWL4030.
>
> This patch series is based off Kevin's tree origin/pm branch.
Hmm, I don't think so. It appears to be based off of Thara's SR
series.
Kevin
next prev parent reply other threads:[~2010-04-06 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 10:19 [PATCH v4 0/5] omap3: pm: Update TRITON power scripts and making it generic Lesly A M
2010-04-06 21:23 ` Kevin Hilman [this message]
2010-04-08 6:25 ` Lesly Arackal Manuel
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=877hoknumc.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=leslyam@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox