public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: [GIT PULL] omap fixes for v3.0-rc3
Date: Fri, 17 Jun 2011 04:13:31 -0700	[thread overview]
Message-ID: <20110617111330.GD23145@atomide.com> (raw)

Hi Linus,

Please pull omap fixes from:

git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git fixes

This set contains regression fixes for PM and pandora board.

Regards,

Tony


The following changes since commit 2c53b436a30867eb6b47dd7bab23ba638d1fb0d2:
  Linus Torvalds (1):
        Linux 3.0-rc3

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git fixes

Grazvydas Ignotas (1):
      omap: pandora: fix NAND support

Kevin Hilman (2):
      OMAP: PM: omap_device: fix device power domain callbacks
      OMAP1: PM: register notifiers with generic clock ops even when !PM_RUNTIME

Russell King (1):
      OMAP: PM debug: fix section mismatch warnings

Tony Lindgren (2):
      Merge branch 'for_3.0/pm-fixes' of ssh://master.kernel.org/.../khilman/linux-omap-pm into fixes
      Merge branch 'fixes-v3.0-rc3' into devel-fixes

 arch/arm/mach-omap1/Makefile             |    4 ++--
 arch/arm/mach-omap1/pm_bus.c             |    8 ++++++--
 arch/arm/mach-omap2/board-omap3pandora.c |    3 ++-
 arch/arm/mach-omap2/pm-debug.c           |    4 ++--
 arch/arm/plat-omap/omap_device.c         |   19 +++++++++++++++++--
 5 files changed, 29 insertions(+), 9 deletions(-)

                 reply	other threads:[~2011-06-17 11:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110617111330.GD23145@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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