Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757261Ab1CaKmP (ORCPT ); Thu, 31 Mar 2011 06:42:15 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:53444 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751774Ab1CaKmO (ORCPT ); Thu, 31 Mar 2011 06:42:14 -0400 Date: Thu, 31 Mar 2011 12:41:52 +0200 From: Ingo Molnar To: Russell King - ARM Linux Cc: Nicolas Pitre , david@lang.hm, Linus Torvalds , Arnd Bergmann , Tony Lindgren , David Brown , lkml , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Catalin Marinas , "H. Peter Anvin" , Thomas Gleixner Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window Message-ID: <20110331104152.GB3723@elte.hu> References: <20110331080634.GA18022@elte.hu> <20110331083044.GB14323@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110331083044.GB14323@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2412 Lines: 58 * Russell King - ARM Linux wrote: > On Thu, Mar 31, 2011 at 10:06:34AM +0200, Ingo Molnar wrote: > > Having strong, effective platform abstractions inside the kernel really helps > > even if the hardware space itself is inevitably fragmented: both powerpc and > > x86 has shown that. Until you realize and appreciate that you really have not > > understood the problem i think. > > No, I think it is the other way around. Folk like me and Nicolas over the > last ten years have put considerable amounts of effort into trying to keep > the ARM support code as clean and maintainable as possible. Absolutely no argument about that, whenever i have read core ARM code it was always a pleasure. You guys are doing a fine job there. What i argued with was what Nicolas said: > > > back in the early days of the PCs, different systems from different > > > vendors had different bus types, peripherals at different addresses, > > > etc. that didn't make all of those vendors systems different > > > architectures, instead those things were varients of the x86 > > > architecture. > > > > Most of them didn't survive. That really helps. It does not matter whether hardware survives or not - most pieces of hardware do not survive. What matters is whether the inevitable hardware-churn is allowed to litter the kernel tree with unmaintainable pieces of crap. You even mention that it's not maintainable to you: > That is true of the common ARM stuff, but there's no way we can do this for > all SoC support - there aren't the hours in the day to provide such a wide > oversight. [...] The problem is the solution: > That's why we have SoC maintainers, and the SoC maintainers have the > responsibility to sort out their own sub-trees. ... which sets the wolves to mind the sheep, so to say. Self-oversight never worked very well (unless you believe in perpetual bank bailouts). So Linus and Thomas (with the genirq hat on) are pushing back, because both of them feel affected negatively by crap. "All is fine" or "it's just natural" do not seem like the right answers to those concerns. Thanks, Ingo -- 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/