Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756419Ab1C3Wpr (ORCPT ); Wed, 30 Mar 2011 18:45:47 -0400 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:42947 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754730Ab1C3Wpq (ORCPT ); Wed, 30 Mar 2011 18:45:46 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 98.234.237.12 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18ZUWIU2CFQ/WVxs5pOq6pC Date: Wed, 30 Mar 2011 15:45:26 -0700 From: Tony Lindgren To: Thomas Gleixner Cc: Linus Torvalds , Arnd Bergmann , Russell King - ARM Linux , David Brown , LKML , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Nicolas Pitre , Catalin Marinas , "Paul E. McKenney" , Ingo Molnar Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window Message-ID: <20110330224526.GM18334@atomide.com> References: <20110317183048.GW7258@atomide.com> <20110318101512.GA15375@n2100.arm.linux.org.uk> <201103301906.42429.arnd@arndb.de> <20110330215434.GI18334@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 35 * Thomas Gleixner [110330 15:22]: > On Wed, 30 Mar 2011, Tony Lindgren wrote: > > > * Thomas Gleixner [110330 14:07]: > > > > > > So one person will be not enough, that needs to be a whole team of > > > experienced people in the very near future to deal with the massive > > > tsunami of crap which is targeted at mainline. If we fail to set that > > > up, then we run into a very ugly maintainability issue in no time. > > > > One thing that will help here and distribute the load is to move > > more things under drivers/ as then we have more maintainers looking > > at the code. > > Guess what's that going to solve? Nothing, nada. > > Really, you move the problem to people who are not prepared to deal > with the wave either. So what's the gain? I guess my point is that with creating more common frameworks people will be using common code. Some examples that come to mind are clock framework, gpiolib, dma engine, runtime PM and so on. Then even arch specific driver code becomes generic and separated from the arch specific code. And then the driver subsystem maintainer can review it easier. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/