From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] drop last omap3 board files for v4.8
Date: Fri, 02 Sep 2016 16:05:26 +0200 [thread overview]
Message-ID: <4327380.4mS7Wg8her@wuerfel> (raw)
In-Reply-To: <20160901154057.y6hib3ckdjppehfl@atomide.com>
On Thursday, September 1, 2016 8:40:57 AM CEST Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [160816 08:53]:
> > The following changes since commit 79cdad3635b3a253d712aba115fa274ef94a8c6b:
> >
> > ir-rx51: use hrtimer instead of dmtimer (2016-06-29 21:54:35 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.8/legacy-signed
> >
> > for you to fetch changes up to e92fc4f04a34a407f5ff8acaa13127c62b7bec07:
> >
> > ARM: OMAP2+: Drop legacy board file for LDP (2016-07-10 23:47:38 -0700)
> >
> > ----------------------------------------------------------------
> > Remove the last two legacy board-*.c files for omap3 for legacy
> > booting for v4.8 to allow making mach-omap2 device tree only for
> > v4.9.
> >
> > We've had Nokia N900 and omap3 LDP board-*.c files remaining
> > while other omap3 devices have been device tree only for quite
> > a while now. Also N900 and LDP have had device tree based booting
> > working for years now, but few drivers for N900 were still only
> > working in legacy only mode until recently. With the remaining
> > issues out of the way, we discussed on the mailing lists that
> > we're finally OK to remove the remaining board-*.c files.
> >
> > For the timing of this pull request, I wanted to wait until
> > v4.8-rc1 is out to make sure the legacy booting still works fine
> > after the merge window before doing it.
> >
> > And for v4.8, let's not touch any other platform data in case we
> > still need to revert for some reason. This makes the revert just a
> > question of adding back the legacy board-*.c files.
> >
> > Then if no issues, we can remove the unused remaining platform
> > data later on for v4.9.
>
> Naturally this can wait for v4.9 merge window too if considered
> too intrusive this late.
I'd prefer to do it as a cleanup for 4.9, and added the pull
request to my todo folder for that now, will get to it along
with the other pull requests.
Arnd
next prev parent reply other threads:[~2016-09-02 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 15:52 [GIT PULL] drop last omap3 board files for v4.8 Tony Lindgren
2016-09-01 15:40 ` Tony Lindgren
2016-09-02 14:05 ` Arnd Bergmann [this message]
2016-09-02 14:57 ` Tony Lindgren
2016-09-02 16:31 ` 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=4327380.4mS7Wg8her@wuerfel \
--to=arnd@arndb.de \
--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).