linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org, Vishwanath Sripathy <vishwanath.bs@ti.com>
Subject: RE: [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support
Date: Fri, 11 Mar 2011 11:24:06 +0530	[thread overview]
Message-ID: <b8444ec8f2cca50e27d088fa8e2e687e@mail.gmail.com> (raw)
In-Reply-To: <87mxl2haoo.fsf@ti.com>

> -----Original Message-----
> From: Kevin Hilman [mailto:khilman@ti.com]
> Sent: Friday, March 11, 2011 3:59 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; vishwanath.bs@ti.com
> Subject: Re: [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP
> support
>
> Hi Santosh,
>
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
> > This series is an attempt to clean-up omap cpufreq driver.
> > 	- The OMAP1 and OMAP2PLUS cpufreq support is split to avoid
> > 	  any #ifdefery
> > 	- Alias clock nodes are added in all OMAP2PLUS clock-data
> > 	  to avoid any cpu_is_xxx() checks
> > 	- The omap2plus_cupfreq support is updated to work on
> > 	  SMP_ON_UP builds
> > 	- SMP support is added which can be used on OMAP4
> >
> > Thanks to Vishwanath BS <vishwanath.bs@ti.com> for doing testing
> > with his DVFS series and review.
>
> Thanks for this series.  I was planning on doing this cleanup as
> well, but it's been a busy development cycle for linux-omap. ;)
>
> After fixing the minor comments, please rebase on latest pm-
> wip/cpufreq
> and I'll add it to that branch.  This probably won't make it for
> 2.6.39, but I'll aim for early in the .40 cycle.
>
Sure. Will do.

Regards,
Santosh

      reply	other threads:[~2011-03-11  5:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  6:10 [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Santosh Shilimkar
2011-02-25  6:10 ` [PATCH 1/3] omap2plus: clock: Add an alias cpu_ck to be used in common cpufreq driver Santosh Shilimkar
2011-03-10 22:13   ` Kevin Hilman
2011-03-14  9:19     ` Santosh Shilimkar
2011-02-25  6:10 ` [PATCH 2/3] omap: cpufreq: Split omap1 and omap2plus cpufreq drivers Santosh Shilimkar
2011-02-25  7:17   ` Vishwanath Sripathy
2011-02-25  7:22     ` Santosh Shilimkar
2011-02-25  8:19   ` DebBarma, Tarun Kanti
2011-02-25  6:10 ` [PATCH 3/3] omap2plus: cpufreq: Add SMP support to cater OMAP4430 Santosh Shilimkar
2011-02-25  8:10   ` DebBarma, Tarun Kanti
2011-03-10 22:27   ` Kevin Hilman
2011-03-10 22:28 ` [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Kevin Hilman
2011-03-11  5:54   ` Santosh Shilimkar [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=b8444ec8f2cca50e27d088fa8e2e687e@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishwanath.bs@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;
as well as URLs for NNTP newsgroup(s).