From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] omap clean-up for v4.2
Date: Fri, 22 May 2015 16:38:47 +0200 [thread overview]
Message-ID: <2834055.EyDA6uXtOP@wuerfel> (raw)
On Wednesday 20 May 2015 15:36:04 Tony Lindgren wrote:
> Clean-up for omaps for v4.2 merge window:
>
> Drop more omap3 legacy board-*.c files for v4.2. This time we're
> dropping the board files for beagle, overo and cm-t35.
>
> The reason for dropping these now rather than later is that now
> we can simply revert the patches in case of unexpected issues as
> we are not dropping any platform data at this point.
>
> This leaves us with only the following board-*.c files:
>
> BOARD REASON NEEDED
> board-ldp.c Still used in RMKs boot test system
> board-omap3logic.c Getting a .dts file for v4.2
> board-omap3pandora.c Got a .dts file for v4.1
> board-rx51-*.c Needs /proc/atags support for user space
>
> I'm hoping we can drop the remaining board-*.c for v4.3 merge
> window, then keep the platform data around for one more merge
> window in case of reverting needed, then drop the platform data
> too for v4.4 if no issues needing reverting are found.
Sounds good.
Pulled into next/cleanup, thanks!
Arnd
next reply other threads:[~2015-05-22 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:38 Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 22:36 [GIT PULL 1/2] omap clean-up for v4.2 Tony Lindgren
2015-05-20 22:36 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=2834055.EyDA6uXtOP@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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