Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754396Ab2HGLhH (ORCPT ); Tue, 7 Aug 2012 07:37:07 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:56164 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754316Ab2HGLhG (ORCPT ); Tue, 7 Aug 2012 07:37:06 -0400 Date: Tue, 7 Aug 2012 12:36:52 +0100 From: Russell King To: Mark Brown Cc: Haojian Zhuang , sameo@linux.intel.com, rpurdie@rpsys.net, bryan.wu@canonical.com, linux-kernel@vger.kernel.org, Bergmann Arnd Subject: Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM Message-ID: <20120807113652.GA6282@flint.arm.linux.org.uk> References: <20120806155805.GR16861@opensource.wolfsonmicro.com> <20120806192209.GA14594@flint.arm.linux.org.uk> <20120806195352.GC16199@opensource.wolfsonmicro.com> <20120806213124.GB14594@flint.arm.linux.org.uk> <20120806220032.GD26698@opensource.wolfsonmicro.com> <20120807103851.GS16861@opensource.wolfsonmicro.com> <20120807111331.GC24257@flint.arm.linux.org.uk> <20120807112844.GZ16861@opensource.wolfsonmicro.com> <20120807113121.GD24257@flint.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120807113121.GD24257@flint.arm.linux.org.uk> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1589 Lines: 44 On Tue, Aug 07, 2012 at 12:31:21PM +0100, Russell King wrote: > On Tue, Aug 07, 2012 at 12:28:44PM +0100, Mark Brown wrote: > > On Tue, Aug 07, 2012 at 12:13:31PM +0100, Russell King wrote: > > > On Tue, Aug 07, 2012 at 11:38:51AM +0100, Mark Brown wrote: > > > > > > If nothing else this seems much more suitable for stable and -rc (the > > > > bug has been there since v3.4). > > > > > There is no need for such hacks. > > > > Please read the text you quoted above. > > I did. > > > > There's no need to botch this in any way what so ever, or invent some > > > other solution only to have to (probably never) rework it. > > > > The changes you're suggesting are extremely invasive for stable > > especially given that we have a simple, driver local, fix available > > *Rubbish*. And, for those hard of thinking, I'll tell you exactly how invasive it is. 1. You modify ioport.h to add the new type. 2. You change the mfd driver creating the resources to use the new type. 3. You change the mfd driver using the resources to call platform_resource_get() with the new type. 4. You get on with life. Yes, it's really that damned simple. Not invasive at all. Mark, you're really making a mountain out of a bloody mole hill over this. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- 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/