From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] OMAP PM fixes for v3.4-rc
Date: Tue, 03 Apr 2012 11:30:22 -0700 [thread overview]
Message-ID: <87zkaspt1d.fsf@ti.com> (raw)
Tony,
Please pull the following OMAP PM fixes for v3.4-rc1.
Thanks,
Kevin
The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
Linux 3.3 (2012-03-18 16:15:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/fixes/pm
for you to fetch changes up to 4ba7c3c3c6567210bf46b1ab3d089134170c2762:
ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1) (2012-03-22 16:11:17 -0700)
----------------------------------------------------------------
Mark A. Greer (2):
arm: omap3: pm34xx.c: Fix omap3_pm_init() error out paths
arm: omap3: pm34xx.c: Replace printk() with appropriate pr_*()
Ming Lei (1):
ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1)
Nishanth Menon (1):
ARM: OMAP2+: OPP: allow OPP enumeration to continue if device is not present
Santosh Shilimkar (1):
ARM: OMAP4: Workaround the OCP synchronisation issue with 32K synctimer.
arch/arm/mach-omap2/opp.c | 4 ++--
arch/arm/mach-omap2/pm34xx.c | 38 ++++++++++++++++++++------------------
arch/arm/mach-omap2/pm44xx.c | 10 ++++++++--
arch/arm/mach-omap2/prm_common.c | 2 +-
4 files changed, 31 insertions(+), 23 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP PM fixes for v3.4-rc
Date: Tue, 03 Apr 2012 11:30:22 -0700 [thread overview]
Message-ID: <87zkaspt1d.fsf@ti.com> (raw)
Tony,
Please pull the following OMAP PM fixes for v3.4-rc1.
Thanks,
Kevin
The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
Linux 3.3 (2012-03-18 16:15:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/fixes/pm
for you to fetch changes up to 4ba7c3c3c6567210bf46b1ab3d089134170c2762:
ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1) (2012-03-22 16:11:17 -0700)
----------------------------------------------------------------
Mark A. Greer (2):
arm: omap3: pm34xx.c: Fix omap3_pm_init() error out paths
arm: omap3: pm34xx.c: Replace printk() with appropriate pr_*()
Ming Lei (1):
ARM: OMAP3+: fix oops triggered in omap_prcm_register_chain_handler(v1)
Nishanth Menon (1):
ARM: OMAP2+: OPP: allow OPP enumeration to continue if device is not present
Santosh Shilimkar (1):
ARM: OMAP4: Workaround the OCP synchronisation issue with 32K synctimer.
arch/arm/mach-omap2/opp.c | 4 ++--
arch/arm/mach-omap2/pm34xx.c | 38 ++++++++++++++++++++------------------
arch/arm/mach-omap2/pm44xx.c | 10 ++++++++--
arch/arm/mach-omap2/prm_common.c | 2 +-
4 files changed, 31 insertions(+), 23 deletions(-)
next reply other threads:[~2012-04-03 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 18:30 Kevin Hilman [this message]
2012-04-03 18:30 ` [GIT PULL] OMAP PM fixes for v3.4-rc Kevin Hilman
2012-04-03 18:43 ` Tony Lindgren
2012-04-03 18:43 ` Tony Lindgren
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=87zkaspt1d.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.