From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] two omap fixes for v4.3-rc cycle
Date: Tue, 20 Oct 2015 12:34:01 -0700 [thread overview]
Message-ID: <20151020193401.GM3078@atomide.com> (raw)
The following changes since commit d8e1f5ed11a39a68da00f05000466c4f6db4456e:
Documentation: ARM: List new omap MMC requirements (2015-10-12 16:23:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.3/fixes-rc6
for you to fetch changes up to 57df5380853460bc66b59a46273ce113c923d39c:
ARM: OMAP2+: Fix imprecise external abort caused by bogus SRAM init (2015-10-19 08:55:46 -0700)
----------------------------------------------------------------
Fixes for omaps for v4.3-rc cycle:
- Fix oops with LPAE and moew than 2GB of memory by enabling
ZONE_DMA for LPAE. Probably no need for stable on this one as we
only recently ran into this with the mainline kernel
- Fix imprecise external abort caused by bogus SRAM init. This affects
dm814x recently merged, so no need for stable on this one AFAIK
----------------------------------------------------------------
Tony Lindgren (2):
ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory
ARM: OMAP2+: Fix imprecise external abort caused by bogus SRAM init
arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 2 +-
arch/arm/boot/dts/omap3-evm-37xx.dts | 2 +-
arch/arm/mach-omap2/Kconfig | 2 ++
arch/arm/mach-omap2/board-generic.c | 10 ++++++++++
arch/arm/mach-omap2/pdata-quirks.c | 9 ++++++++-
5 files changed, 22 insertions(+), 3 deletions(-)
next reply other threads:[~2015-10-20 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 19:34 Tony Lindgren [this message]
2015-10-21 15:02 ` [GIT PULL] two omap fixes for v4.3-rc cycle Arnd Bergmann
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=20151020193401.GM3078@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).