From mboxrd@z Thu Jan 1 00:00:00 1970 From: nico@fluxnic.net (Nicolas Pitre) Date: Sat, 19 May 2012 20:45:03 -0400 (EDT) Subject: [PATCH] arm: Add basic support for new Marvell Armada SoC family In-Reply-To: <201205191732.32384.arnd@arndb.de> References: <1337072084-21967-1-git-send-email-thomas.petazzoni@free-electrons.com> <20120519112431.GH24238@titan.lakedaemon.net> <201205191732.32384.arnd@arndb.de> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sat, 19 May 2012, Arnd Bergmann wrote: > On Saturday 19 May 2012, Jason Cooper wrote: > > > Board files in mach-mvebu and the rest in plat-mvebu. That would match > > > the spirit of the current split between mach-* and plat-*. > > > > Took the words right out of my mouth. Once DT conversions are complete, > > mach-*/ would either go away, or hold legacy non-DT boards. > > > > On a side note, I also like this because it would make converting old > > board files like sheevaplug and guruplug to DT easier. The legacy > > implementation would be in mach-mvebu/ and the DT implementation would > > be in plat-mvebu/. Newcomers to the code would see a clearly defined > > separation. > > With that layout, where do the mach/* headers go? I think arch/arm/plat-mvvebu/include/mach/* could work. Nicolas