linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/6] omap pm changes for v3.11 merge window
Date: Wed, 12 Jun 2013 11:24:34 -0700	[thread overview]
Message-ID: <E1UmpjQ-0005cT-Lo@merlin.infradead.org> (raw)
In-Reply-To: <pull-1371061475-206272>

The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:

  Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.11/pm-signed

for you to fetch changes up to 49a34fd5380d249ae8a2173399c62fc5a1fddd70:

  Merge tag 'omap-pm-v3.10/cleanup/pm' of git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm into omap-for-v3.11/pm (2013-05-16 08:27:49 -0700)

----------------------------------------------------------------

Omap PM changes via Kevin Hilman <khilman@linaro.org>:

OMAP PM cleanups for v3.10

----------------------------------------------------------------
Santosh Shilimkar (4):
      ARM: OMAP4: PM: Avoid expensive cpu_suspend() path for all CPU power states except off
      ARM: OMAP4+: PM: Consolidate MPU subsystem PM code for re-use
      ARM: OMAP4+: Make secondary_startup function name more consistent
      ARM: OMAP4+: PM: Consolidate OMAP4 PM code to re-use it for OMAP5

Tony Lindgren (1):
      Merge tag 'omap-pm-v3.10/cleanup/pm' of git://git.kernel.org/.../khilman/linux-omap-pm into omap-for-v3.11/pm

 arch/arm/mach-omap2/common.h              |  4 +-
 arch/arm/mach-omap2/omap-headsmp.S        |  8 ++--
 arch/arm/mach-omap2/omap-mpuss-lowpower.c | 69 +++++++++++++++++++++++++------
 arch/arm/mach-omap2/omap-smp.c            |  6 +--
 arch/arm/mach-omap2/pm44xx.c              | 58 +++++++++++++++++++++-----
 5 files changed, 113 insertions(+), 32 deletions(-)

  parent reply	other threads:[~2013-06-12 18:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pull-1371061475-206272>
2013-06-12 18:24 ` [GIT PULL 2/6] omap cleanup for v3.11 merge window Tony Lindgren
2013-06-12 18:24 ` Tony Lindgren [this message]
2013-06-12 18:24 ` [GIT PULL 4/6] omap gpmc changes " Tony Lindgren
2013-06-12 18:24 ` [GIT PULL 5/6] omap soc " Tony Lindgren
2013-06-12 18:24 ` [GIT PULL 6/6] omap5 data " Tony Lindgren
2013-06-14 21:36   ` Olof Johansson
2013-06-17 10:37     ` Tony Lindgren
     [not found] ` <51b8bce9.1265310a.49c1.ffff940eSMTPIN_ADDED_MISSING@mx.google.com>
2013-06-14 21:28   ` [GIT PULL 2/6] omap cleanup " Olof Johansson
2013-06-17 10:33     ` Tony Lindgren
     [not found] ` <51b8bcea.46dbe00a.6f0b.fffffdf1SMTPIN_ADDED_MISSING@mx.google.com>
2013-06-14 21:35   ` [GIT PULL 3/6] omap pm changes " Olof Johansson
     [not found] ` <51b8bcec.41ace00a.4b4c.0772SMTPIN_ADDED_MISSING@mx.google.com>
2013-06-14 21:35   ` [GIT PULL 5/6] omap soc " Olof Johansson
     [not found] ` <51b8bceb.d447310a.2e65.ffff937fSMTPIN_ADDED_MISSING@mx.google.com>
2013-06-14 21:37   ` [GIT PULL 4/6] omap gpmc " Olof Johansson

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=E1UmpjQ-0005cT-Lo@merlin.infradead.org \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).