From: Nishanth Menon <nm@ti.com>
To: Linux-omap <linux-omap@vger.kernel.org>
Cc: "Rajendra Nayak" <rnayak@ti.com>,
"Roger Quadros" <ext-roger.quadros@nokia.com>,
"Kalle Jokiniemi" <ext-kalle.jokiniemi@nokia.com>,
"Teerth Reddy" <teerth@ti.com>,
"Kevin Hilman" <khilman@deeprootsystems.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Högander Jouni" <jouni.hogander@nokia.com>,
"Imberton Guilhem" <guilhem.imberton@motorola.com>,
"Mike Chan" <mikechan@google.com>
Subject: Re: [RFC][PATCH 0/2] OMAP3:PM:SR Refactor
Date: Thu, 1 Oct 2009 19:40:10 -0500 [thread overview]
Message-ID: <4AC54BEA.8080307@ti.com> (raw)
In-Reply-To: <1254443465-13006-1-git-send-email-nm@ti.com>
Menon, Nishanth had written, on 10/01/2009 07:31 PM, the following:
> Hi,
> Smart Reflex sequencing recommendation has improved
> in recent times and presents an opportunity to refactor
> the code to add in understanding that we have of the
> system. The patch set replaces smartreflex.c with a
> new revision.
>
> This revision is meant to be RFC due to the nature of
> intrusive changes done
>
> Nishanth Menon (2):
> OMAP3:PM:SR: prepare: remove old SR code
> OMAP3:PM:SR: SmartReflex Refactor Rev2.0
>
> arch/arm/mach-omap2/resource34xx.c | 8 +-
> arch/arm/mach-omap2/smartreflex.c | 1899 +++++++++++++++++++++---------------
> arch/arm/mach-omap2/smartreflex.h | 241 +++---
> arch/arm/plat-omap/Kconfig | 18 +-
> 4 files changed, 1249 insertions(+), 917 deletions(-)
Should have added that the patches are against commit ID
f3ba1f772ebf69fa8765aa2e4b2fbcd3e78c1081 on [1] pm branch
--
Regards,
Nishanth Menon
Ref:
[1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git
prev parent reply other threads:[~2009-10-02 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 0:31 [RFC][PATCH 0/2] OMAP3:PM:SR Refactor Nishanth Menon
2009-10-02 0:31 ` [RFC][PATCH 1/2] OMAP3:PM:SR: prepare: remove old SR code Nishanth Menon
2009-10-02 0:31 ` [RFC][PATCH 2/2] OMAP3:PM:SR: SmartReflex Refactor Rev2.0 Nishanth Menon
2009-10-02 14:30 ` Kevin Hilman
2009-10-09 21:37 ` Kevin Hilman
2009-10-09 21:50 ` Nishanth Menon
2009-10-02 0:40 ` Nishanth Menon [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=4AC54BEA.8080307@ti.com \
--to=nm@ti.com \
--cc=ext-kalle.jokiniemi@nokia.com \
--cc=ext-roger.quadros@nokia.com \
--cc=guilhem.imberton@motorola.com \
--cc=jouni.hogander@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mikechan@google.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=teerth@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