From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: [GIT PULL] omap fixes against v3.18-rc2
Date: Thu, 30 Oct 2014 09:50:20 -0700 [thread overview]
Message-ID: <20141030165019.GA31454@atomide.com> (raw)
The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fixes-against-v3.18-rc2
for you to fetch changes up to 4b91f7f3c8b20e073b7bfc098625b37f99789508:
ARM: OMAP2+: Warn about deprecated legacy booting mode (2014-10-29 12:19:20 -0700)
----------------------------------------------------------------
Few fixes for omaps to enable NAND BCH so devices won't
produce errors when booted with omap2plus_defconfig, and
reduce bloat by making IPV6 a loadable module.
Also let's add a warning about legacy boot being deprecated
for omap3.
We now have things working with device tree, and only omap3 is
still booting in legacy mode. So hopefully this warning will
help move the remaining legacy mode users to boot with device
tree.
As the total reduction of code and static data is somewhere
around 20000 lines of code once we remove omap3 legacy mode
booting, we really do want to make omap3 to boot also in
device tree mode only over the next few merge cycles.
----------------------------------------------------------------
Tony Lindgren (3):
ARM: omap2plus_defconfig: Fix bloat caused by having ipv6 built-in
ARM: omap2plus_defconfig: Fix errors with NAND BCH
ARM: OMAP2+: Warn about deprecated legacy booting mode
arch/arm/configs/omap2plus_defconfig | 4 ++--
arch/arm/mach-omap2/omap_device.c | 4 ++++
2 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2014-10-30 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 16:50 Tony Lindgren [this message]
2014-11-02 21:39 ` [GIT PULL] omap fixes against v3.18-rc2 Olof Johansson
2014-11-02 23:53 ` 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=20141030165019.GA31454@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).