From mboxrd@z Thu Jan 1 00:00:00 1970 From: tglx@linutronix.de (Thomas Gleixner) Date: Thu, 31 Mar 2011 00:56:33 +0200 (CEST) Subject: [GIT PULL] omap changes for v2.6.39 merge window In-Reply-To: <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> <20110330224526.GM18334@atomide.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, 30 Mar 2011, Tony Lindgren wrote: > * 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. For all that to happen you need a really experienced team with a strong team lead to fight that through and go through the existing horror while dealing with the incoming flood at the same time. See commit 9ad198cb for illustration. Sigh, I fought that battle for a couple of month to deal with shite coming in faster than you can fix it and everyone ignoring it. Thanks, tglx