Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753889Ab1CKUM6 (ORCPT ); Fri, 11 Mar 2011 15:12:58 -0500 Received: from www.tglx.de ([62.245.132.106]:48245 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751465Ab1CKUM4 (ORCPT ); Fri, 11 Mar 2011 15:12:56 -0500 Date: Fri, 11 Mar 2011 21:12:13 +0100 (CET) From: Thomas Gleixner To: Mark Brown cc: Abhijeet Dharmapurikar , davidb@codeaurora.org, "David S. Miller" , Andrew Morton , Bryan Huntsman , Daniel Walker , David Collins , Grant Likely , Greg Kroah-Hartman , Joe Perches , Russell King , Samuel Ortiz , Stepan Moskovchenko , Linus Walleij , linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, LKML Subject: Re: [Qualcomm PM8921 MFD v2 2/6] mfd: pm8xxx: Add irq support In-Reply-To: <20110311195719.GX1760@opensource.wolfsonmicro.com> Message-ID: References: <1299564590-30116-1-git-send-email-adharmap@codeaurora.org> <1299564590-30116-3-git-send-email-adharmap@codeaurora.org> <4D770E47.6050402@codeaurora.org> <4D79A85D.8000301@codeaurora.org> <4D7A71B9.9000306@codeaurora.org> <20110311195719.GX1760@opensource.wolfsonmicro.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 40 On Fri, 11 Mar 2011, Mark Brown wrote: > On Fri, Mar 11, 2011 at 08:43:08PM +0100, Thomas Gleixner wrote: > > > Sigh, why insist people on working around core code instead of talking > > to the responsible maintainers about their problem in the first place? > > I don't know if it's the case here but with a lot of the people I speak > to it's because they're used to working on proprietary OSs where there's > no possibility of fixing the core and they haven't yet realised that > this is a possibility. Good point. If I only knew a way to get this message to those folks once and forever. There are several good reasons to avoid working around core code: - It's usually simpler and faster as the core code has all the necessary information. So that's even an argument which managers might understand. - Such workarounds, when not caught, tend to spread themself magically because driver writers checkout the existing code of similar devices and copy/paste/modify^Wuglify them over and over. - In the worst case such workarounds make the core maintainence harder and in some cases impossible, because they silently imply semantics on the core w/o the core maintainer knowing about them. I'm going to give a talk about that at the collab summit :) Thanks, tglx -- 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/