From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] omap legacy boot clean-up for v4.1
Date: Thu, 19 Mar 2015 16:14:01 -0700 [thread overview]
Message-ID: <pull-1426799683-420388-3> (raw)
In-Reply-To: <pull-1426799683-420388>
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/v4.1-legacy
for you to fetch changes up to 01ea0d4247bb3a224a66007e0a1291232c15d61a:
ARM: OMAP2+: Remove legacy support for omap3 TouchBook (2015-03-16 17:07:26 -0700)
----------------------------------------------------------------
Drop three omap3 legacy board-*.c files
We want to get omap3 moved over to device tree only based booting.
These three board-*.c files seem to be inactive, so let's attempt
to drop them now rather than later. With these dropped, we have
omap3 device tree conversion status in a known state. Then we know
that we have .dts support for the remaining omap3 board-*.c files,
or it's being worked on.
By dropping these files now, we can simply revert them if really
needed for the next few merge cycles if we run into suprises.
Reverting things later on will not be so easily done.
----------------------------------------------------------------
Tony Lindgren (3):
ARM: OMAP3: Remove legacy support for EMA-Tech Stalker board
ARM: OMAP3: Remove legacy support for devkit8000
ARM: OMAP2+: Remove legacy support for omap3 TouchBook
arch/arm/mach-omap2/Kconfig | 18 -
arch/arm/mach-omap2/Makefile | 4 -
arch/arm/mach-omap2/board-devkit8000.c | 654 -----------------------------
arch/arm/mach-omap2/board-omap3stalker.c | 433 -------------------
arch/arm/mach-omap2/board-omap3touchbook.c | 395 -----------------
5 files changed, 1504 deletions(-)
delete mode 100644 arch/arm/mach-omap2/board-devkit8000.c
delete mode 100644 arch/arm/mach-omap2/board-omap3stalker.c
delete mode 100644 arch/arm/mach-omap2/board-omap3touchbook.c
next prev parent reply other threads:[~2015-03-19 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 23:13 [GIT PULL 1/3] omap device tree changes for v4.1, part1 Tony Lindgren
2015-03-19 23:14 ` [GIT PULL 2/3] omap defconfig changes for v4.1 Tony Lindgren
2015-03-19 23:14 ` Tony Lindgren [this message]
[not found] ` <550b5961.65f8420a.142c.ffff9cfeSMTPIN_ADDED_BROKEN@mx.google.com>
2015-04-03 17:50 ` Olof Johansson
[not found] ` <550b5960.65f8420a.142c.ffff9cddSMTPIN_ADDED_BROKEN@mx.google.com>
2015-04-03 17:51 ` [GIT PULL 3/3] omap legacy boot clean-up " Olof Johansson
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=pull-1426799683-420388-3 \
--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