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 2/7] omap device changes for v3.7 merge window
Date: Thu, 13 Sep 2012 19:34:10 -0700 [thread overview]
Message-ID: <E1TCLk2-0006Tj-Rw@merlin.infradead.org> (raw)
In-Reply-To: <pull-1347590052-683636>
The following changes since commit 55d512e245bc7699a8800e23df1a24195dd08217:
Linux 3.6-rc5 (2012-09-08 16:43:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/devel-omap-device-for-v3.7
for you to fetch changes up to 47d85ec2a23552fd3d8b56778a23a5a843c5b9b1:
Merge tag 'for_3.7-omap_device' of git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm into devel-omap-device (2012-09-12 21:17:56 -0700)
----------------------------------------------------------------
Kevin Hilman <khilman@ti.com>:
Updates for omap_device layer for v3.7.
Allows omap_device layer to keep track of driver bound status in order
to make more intelligent decisions about idling unused devices.
----------------------------------------------------------------
Kevin Hilman (3):
ARM: OMAP: omap_device: keep track of driver bound status
ARM: OMAP: omap_device: don't attempt late suspend if no driver bound
ARM: OMAP: omap_device: idle devices with no driver bound
Tony Lindgren (1):
Merge tag 'for_3.7-omap_device' of git://git.kernel.org/.../khilman/linux-omap-pm into devel-omap-device
arch/arm/plat-omap/include/plat/omap_device.h | 2 +
arch/arm/plat-omap/omap_device.c | 56 ++++++++++++++++++++++---
2 files changed, 53 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2012-09-14 2:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 2:34 [GIT PULL 1/7] omap non-critical fixes for v3.7 merge window Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 3/7] omap gpmc cleanup " Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 2/7] omap device changes " Tony Lindgren
2012-09-14 2:34 ` Tony Lindgren [this message]
2012-09-14 2:34 ` [GIT PULL 3/7] omap gpmc cleanup " Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 4/7] omap custom atag removal " Tony Lindgren
2012-09-14 2:34 ` Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 5/7] omap sparse irq and local hardware.h cleanup " Tony Lindgren
2012-09-14 2:34 ` Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 6/7] omap makefile and sparse " Tony Lindgren
2012-09-14 2:34 ` Tony Lindgren
2012-09-17 3:08 ` Olof Johansson
2012-09-17 3:08 ` Olof Johansson
2012-09-14 2:34 ` [GIT PULL 7/7] am33xx hwmod data " Tony Lindgren
2012-09-14 2:34 ` Tony Lindgren
[not found] ` <E1TCLkq-0006f8-Qp@merlin.infradead.org>
2012-09-14 17:55 ` [GIT PULL 5/7] omap sparse irq and local hardware.h cleanup " Tony Lindgren
2012-09-14 17:55 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2012-09-14 2:18 [GIT PULL 1/7] omap non-critical fixes " Tony Lindgren
2012-09-14 2:18 ` [GIT PULL 2/7] omap device changes " Tony Lindgren
2012-09-14 2:18 ` Tony Lindgren
[not found] ` <5052940c.c8cae00a.65bd.ffffc8b2SMTPIN_ADDED@mx.google.com>
2012-09-17 2:51 ` Olof Johansson
2012-09-17 2:51 ` 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=E1TCLk2-0006Tj-Rw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.