On Tuesday 09 April 2013, Tony Lindgren wrote:
> The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
> 
>   Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap 
> tags/omap-for-v3.10/cleanup-pm-signed
> 
> for you to fetch changes up to ca8cdff548da76da01f3783548ceb917139a5ddc:
> 
>   Merge tag 'omap-pm-v3.10/cleanup/cpuidle' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm into 
> omap-for-v3.10/cleanup-pm (2013-04-08 09:51:00 -0700)
> 
> ----------------------------------------------------------------
> 
> PM cleanup to prepare for omap5 PM via Kevin Hilman <[email protected]>:
> 
> OMAP3/4 CPUidle cleanups for v3.10

Adding Daniel and Rafael to Cc.

Is this series coordinated with the other cpuidle changes? Please tell me if 
this
is good to go into arm-soc.

        Arnd

> ----------------------------------------------------------------
> Daniel Lezcano (1):
>       ARM: omap3: cpuidle: enable time keeping
> 
> Santosh Shilimkar (5):
>       ARM: OMAP4: CPUidle: Avoid double idle driver registration
>       ARM: OMAP: CPUidle: Unregister drivere on device registration failure
>       ARM: OMAP4: CPUidle: Make C-state description field more precise
>       ARM: OMAP4+: CPUidle: Deprecate use of 
> omap4_mpuss_read_prev_context_state()
>       ARM: OMAP4+: CPUidle: Consolidate idle driver for OMAP5 support
> 
> Tony Lindgren (1):
>       Merge tag 'omap-pm-v3.10/cleanup/cpuidle' of 
> git://git.kernel.org/.../khilman/linux-omap-pm into omap-for-v3.10/cleanup-pm
> 
>  arch/arm/mach-omap2/common.h              |  5 ----
>  arch/arm/mach-omap2/cpuidle34xx.c         | 11 +++++--
>  arch/arm/mach-omap2/cpuidle44xx.c         | 48 
> +++++++++++++++++--------------
>  arch/arm/mach-omap2/omap-mpuss-lowpower.c | 14 ---------
>  4 files changed, 35 insertions(+), 43 deletions(-)
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to