From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756748Ab1CaGm3 (ORCPT ); Thu, 31 Mar 2011 02:42:29 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:65241 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775Ab1CaGm1 convert rfc822-to-8bit (ORCPT ); Thu, 31 Mar 2011 02:42:27 -0400 MIME-Version: 1.0 X-Originating-IP: [172.22.72.244] In-Reply-To: References: <20110317183048.GW7258@atomide.com> <20110318101512.GA15375@n2100.arm.linux.org.uk> <201103301906.42429.arnd@arndb.de> <20110331001502.GB6680@n2100.arm.linux.org.uk> Date: Wed, 30 Mar 2011 23:42:26 -0700 Message-ID: Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window From: Olof Johansson To: Linus Torvalds Cc: Bill Gatliff , Russell King - ARM Linux , Arnd Bergmann , Tony Lindgren , David Brown , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Nicolas Pitre , Catalin Marinas Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 30, 2011 at 8:24 PM, Linus Torvalds wrote: > Check out the device tree files (*.dts) and do that same > >   git ls-files arch/arm/ | grep gpio > > except do it on powerpc. > > See the difference? > > The powerpc people even wrote documentation about the thing, which is > just above and beyond reasonable. Powerpc does has the benefit of only having about three (active) silicon vendors, out of which two are doing most of the arch infrastructure work. There are more chefs in the kitchen in the ARM world. But yeah, the arch/powerpc/platforms/* directories are tiny compared to the ARM equivalents. That being said: arch/ppc used to be messy too. A lot of cleanups were done when the ppc+ppc64 -> powerpc merge happened. Starting over on a new base would avoid some of the problems of dealing with new incoming platforms while things are being cleaned up. It would decouple need to start reviewing _everything_ at the same time as as the cleanup is underway, and would give a chance to set good examples for how things should be handled as new platforms are brought over. Then, when the time comes, start refusing new boards/SoCs/features on the old subtree and have new clean stuff go directly into the new one. Of course, main drawback is that this would duplicate the actual arch code (the parts Russell are handling), and he is already stretched thin as it is. That code isn't what needs the cleanup most though, so maybe it can just be shared to start with to avoid that overhead. -Olof