mbox

[GIT,PULL] cpufreq: OMAP: move to drivers/cpufreq and updates for v3.3

Message ID 871ut5w2js.fsf@ti.com
State New
Headers show

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.3/omap-cpufreq

Message

Kevin Hilman Nov. 18, 2011, 9:20 p.m. UTC
Hi Dave,

Here's the updated pull request after a rebase onto v3.2-rc1 and some
fixes to address other changes that went into v3.2.

This is targetted for v3.3, so I'd like to get it into your tree and
into linux-next.

Also, let me know if you want a MAINTAINERS entry for this file, as I'm
happy to maintain it.

Kevin


The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:

  Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.3/omap-cpufreq

Colin Cross (1):
      cpufreq: OMAP: notify even with bad boot frequency

Kevin Hilman (1):
      cpufreq: OMAP: fixup for omap_device changes, include <linux/module.h>

Nishanth Menon (6):
      cpufreq: OMAP: move clk name decision to init
      cpufreq: OMAP: deny initialization if no mpudev
      cpufreq: OMAP: dont support !freq_table
      cpufreq: OMAP: only supports OPP library
      cpufreq: OMAP: put clk if cpu_init failed
      cpufreq: OMAP: fix freq_table leak

Russell King (1):
      cpufreq: OMAP: Add SMP support for OMAP4+

Santosh Shilimkar (1):
      cpufreq: OMAP: cleanup for multi-SoC support, move into drivers/cpufreq

Todd Poynor (1):
      cpufreq: OMAP: Enable all CPUs in shared policy mask

 arch/arm/plat-omap/Makefile    |    1 -
 arch/arm/plat-omap/cpu-omap.c  |  171 -------------------------
 drivers/cpufreq/Makefile       |    1 +
 drivers/cpufreq/omap-cpufreq.c |  274 ++++++++++++++++++++++++++++++++++++++++
 4 files changed, 275 insertions(+), 172 deletions(-)
 delete mode 100644 arch/arm/plat-omap/cpu-omap.c
 create mode 100644 drivers/cpufreq/omap-cpufreq.c

Comments

Kevin Hilman Dec. 2, 2011, 5:45 p.m. UTC | #1
Dave,

Kevin Hilman <khilman@ti.com> writes:

> Hi Dave,
>
> Here's the updated pull request after a rebase onto v3.2-rc1 and some
> fixes to address other changes that went into v3.2.
>
> This is targetted for v3.3, so I'd like to get it into your tree and
> into linux-next.

Are there any problems with this series or pull request?  

Kevin

> Also, let me know if you want a MAINTAINERS entry for this file, as I'm
> happy to maintain it.
>
> Kevin
>
>
> The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:
>
>   Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)
>
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.3/omap-cpufreq
>
> Colin Cross (1):
>       cpufreq: OMAP: notify even with bad boot frequency
>
> Kevin Hilman (1):
>       cpufreq: OMAP: fixup for omap_device changes, include <linux/module.h>
>
> Nishanth Menon (6):
>       cpufreq: OMAP: move clk name decision to init
>       cpufreq: OMAP: deny initialization if no mpudev
>       cpufreq: OMAP: dont support !freq_table
>       cpufreq: OMAP: only supports OPP library
>       cpufreq: OMAP: put clk if cpu_init failed
>       cpufreq: OMAP: fix freq_table leak
>
> Russell King (1):
>       cpufreq: OMAP: Add SMP support for OMAP4+
>
> Santosh Shilimkar (1):
>       cpufreq: OMAP: cleanup for multi-SoC support, move into drivers/cpufreq
>
> Todd Poynor (1):
>       cpufreq: OMAP: Enable all CPUs in shared policy mask
>
>  arch/arm/plat-omap/Makefile    |    1 -
>  arch/arm/plat-omap/cpu-omap.c  |  171 -------------------------
>  drivers/cpufreq/Makefile       |    1 +
>  drivers/cpufreq/omap-cpufreq.c |  274 ++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 275 insertions(+), 172 deletions(-)
>  delete mode 100644 arch/arm/plat-omap/cpu-omap.c
>  create mode 100644 drivers/cpufreq/omap-cpufreq.c
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Dave Jones Dec. 2, 2011, 5:52 p.m. UTC | #2
On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
 > Dave,
 > 
 > Kevin Hilman <khilman@ti.com> writes:
 > 
 > > Hi Dave,
 > >
 > > Here's the updated pull request after a rebase onto v3.2-rc1 and some
 > > fixes to address other changes that went into v3.2.
 > >
 > > This is targetted for v3.3, so I'd like to get it into your tree and
 > > into linux-next.
 > 
 > Are there any problems with this series or pull request?  

Somehow I missed this. I'll get to it this afternoon and push it out.

apologies.

	Dave.
Dave Jones Dec. 2, 2011, 7:45 p.m. UTC | #3
On Fri, Dec 02, 2011 at 12:52:57PM -0500, Dave Jones wrote:
 > On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
 >  > Dave,
 >  > 
 >  > Kevin Hilman <khilman@ti.com> writes:
 >  > 
 >  > > Hi Dave,
 >  > >
 >  > > Here's the updated pull request after a rebase onto v3.2-rc1 and some
 >  > > fixes to address other changes that went into v3.2.
 >  > >
 >  > > This is targetted for v3.3, so I'd like to get it into your tree and
 >  > > into linux-next.
 >  > 
 >  > Are there any problems with this series or pull request?  
 > 
 > Somehow I missed this. I'll get to it this afternoon and push it out.

applied and pushed.

So things have seemed kinda quiet lately, which is making me wonder if
I've somehow lost other mail too.  (There have been a number of small disasters
with my @redhat mail this last month).

If anyone has anything else pending that hasn't been applied yet, please resend,
and I'll get on top of it asap.

	Dave
Kevin Hilman Dec. 2, 2011, 9:19 p.m. UTC | #4
Dave Jones <davej@redhat.com> writes:

> On Fri, Dec 02, 2011 at 12:52:57PM -0500, Dave Jones wrote:
>  > On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
>  >  > Dave,
>  >  > 
>  >  > Kevin Hilman <khilman@ti.com> writes:
>  >  > 
>  >  > > Hi Dave,
>  >  > >
>  >  > > Here's the updated pull request after a rebase onto v3.2-rc1 and some
>  >  > > fixes to address other changes that went into v3.2.
>  >  > >
>  >  > > This is targetted for v3.3, so I'd like to get it into your tree and
>  >  > > into linux-next.
>  >  > 
>  >  > Are there any problems with this series or pull request?  
>  > 
>  > Somehow I missed this. I'll get to it this afternoon and push it out.
>
> applied and pushed.
>

Thanks!

Kevin