From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] few omap fixes for v3.8-rc2
Date: Tue, 8 Jan 2013 09:48:16 -0800 [thread overview]
Message-ID: <20130108174816.GP14149@atomide.com> (raw)
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.8-rc2/fixes-signed-v2
for you to fetch changes up to 6adba67eb0c4731ed0346731d024b2102f5b4d9d:
ARM: OMAP2+: am33xx-hwmod: Fix wrongly terminated am33xx_usbss_mpu_irqs array (2013-01-07 12:38:07 -0800)
----------------------------------------------------------------
The biggest change is a fix to deal with different power state
on omap2 registers that causes issues trying to use common PM code.
Also fix few incorrect registers, and an issue for omap1 USB, and
few sparse fixes for issues that sneaked in with all the clean-up.
----------------------------------------------------------------
Aaro Koskinen (1):
ARM: OMAP1: fix USB configuration use-after-release
Ivan Khoronzhuk (2):
ARM: OMAP4: PRM: Correct reset source map
ARM: OMAP4: PRM: Correct wrong instance usage for reading reset sources
Jon Hunter (1):
ARM: OMAP3: clock data: Add missing enable/disable for EMU clock
Nishanth Menon (1):
ARM: OMAP4: PRM: fix RSTTIME and RSTST offsets
Pantelis Antoniou (1):
ARM: OMAP2+: am33xx-hwmod: Fix wrongly terminated am33xx_usbss_mpu_irqs array
Paul Walmsley (4):
ARM: OMAP: 32k counter: resolve sparse warnings
ARM: OMAP AM33xx: hwmod data: resolve sparse warnings
ARM: OMAP: SRAM: resolve sparse warnings
ARM: OMAP2/3: PRM: fix bogus OMAP2xxx powerstate return values
Tony Lindgren (1):
Merge tag 'omap-fixes-a2-for-v3.8-rc' of git://git.kernel.org/.../pjw/omap-pending into omap-for-v3.8-rc2/fixes
arch/arm/mach-omap1/board-ams-delta.c | 2 +-
arch/arm/mach-omap1/usb.c | 8 ++-
arch/arm/mach-omap2/cclock3xxx_data.c | 2 +
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 6 +-
arch/arm/mach-omap2/prm2xxx.c | 88 +++++++++++++++++++++++++++++-
arch/arm/mach-omap2/prm2xxx_3xxx.c | 22 --------
arch/arm/mach-omap2/prm3xxx.c | 28 +++++++++-
arch/arm/mach-omap2/prm44xx.c | 6 +-
arch/arm/mach-omap2/prm44xx.h | 4 +-
arch/arm/plat-omap/counter_32k.c | 2 +
arch/arm/plat-omap/sram.c | 2 +
11 files changed, 132 insertions(+), 38 deletions(-)
next reply other threads:[~2013-01-08 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 17:48 Tony Lindgren [this message]
2013-01-08 18:01 ` [GIT PULL] few omap fixes for v3.8-rc2 Olof Johansson
2013-01-08 18:20 ` 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=20130108174816.GP14149@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).