From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: PM fixes for v3.7-rc3
Date: Tue, 23 Oct 2012 18:37:01 -0700 [thread overview]
Message-ID: <20121024013700.GB5605@atomide.com> (raw)
In-Reply-To: <87d3087s5k.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [121023 15:15]:
> Tony,
>
> Here are a few more fixes PM-related fixes for v3.7-rc
>
> Kevin
>
>
> The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
>
> Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git tags/for_3.7-rc3-fixes-pm
>
> for you to fetch changes up to 65bf7ca0005d7d827596d5df28583c83c9158da6:
>
> ARM: OMAP3: Beagle: fix OPP customization and initcall ordering (2012-10-22 16:01:42 -0700)
>
> ----------------------------------------------------------------
> Misc. OMAP PM-related fixes for v3.7-rc
Thanks pulling into omap-for-v3.7-rc1/fixes.
Regards,
Tony
> ----------------------------------------------------------------
> Kevin Hilman (2):
> ARM: OMAP2: UART: fix console UART mismatched runtime PM status
> ARM: OMAP3: Beagle: fix OPP customization and initcall ordering
>
> Paul Walmsley (1):
> ARM: OMAP3: PM: apply part of the erratum i582 workaround
>
> arch/arm/mach-omap2/board-omap3beagle.c | 22 +++++++++++++---------
> arch/arm/mach-omap2/pm.h | 1 +
> arch/arm/mach-omap2/pm34xx.c | 30 ++++++++++++++++++++++++++++--
> arch/arm/mach-omap2/serial.c | 5 +++++
> 4 files changed, 47 insertions(+), 11 deletions(-)
prev parent reply other threads:[~2012-10-24 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 22:14 [GIT PULL] ARM: OMAP: PM fixes for v3.7-rc3 Kevin Hilman
2012-10-24 1:37 ` Tony Lindgren [this message]
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=20121024013700.GB5605@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).