[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10084728.p75H39SaXO@wuerfel>
Date: Wed, 02 Dec 2015 22:15:02 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Andrew Lunn <andrew@...n.ch>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Jason Cooper <jason@...edaemon.net>,
Benjamin Cama <benoar@...ka.fr>, linux-kernel@...r.kernel.org,
Detlef Vollmann <dv@...lmann.ch>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH 0/5] ARM: orion5x/dove/mv78xx0 multiplatform
On Wednesday 02 December 2015 21:38:10 Andrew Lunn wrote:
> On Wed, Dec 02, 2015 at 08:22:40PM +0000, Russell King - ARM Linux wrote:
> > On Wed, Dec 02, 2015 at 08:51:04PM +0100, Arnd Bergmann wrote:
> > > I'm mostly interested in it because it's the only ARMv7 platform that is
> > > left after my other patches, and I just want to be done with it after
> > > spending 5 years on it
> >
> > My understanding is that the long term goal is to delete mach-dove once
> > everyone has settled down into the mvebu DT world.
> >
> > Right now we have mvebu which covers Dove using DT. We have mach-dove
> > which is legacy non-DT Dove.
> >
> > It seems to me to be completely crazy to want to bring legacy code, which
> > is ultimately destined to be deleted, into multiplatform.
>
> I agree. We have multiplatform dove already, it is in mach-mvebu. Do
> we really need both mach-dove and mach-mvebu dove in one kernel?
I'm also fine with deleting mach-dove, but that would be much more
disruptive to Russell's work, so I don't think that helps anyone.
I've rebased the series to leave out the last two patches for dove,
and added the watchdog on dove, so I can at least get the other
patches out of my queue if that works for now.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists