Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758119Ab0BXUlA (ORCPT ); Wed, 24 Feb 2010 15:41:00 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:59135 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758024Ab0BXUk6 (ORCPT ); Wed, 24 Feb 2010 15:40:58 -0500 Date: Wed, 24 Feb 2010 20:40:56 +0000 From: Mark Brown To: Dmitry Torokhov Cc: Liam Girdwood , linux-kernel@vger.kernel.org Subject: Re: [PATCH 13/14] Regulators: wm8400 - cleanup platform driver data handling Message-ID: <20100224204056.GA6824@rakim.wolfsonmicro.main> References: <20100224073342.15964.8863.stgit@localhost.localdomain> <20100224073849.15964.62321.stgit@localhost.localdomain> <20100224102548.GG18896@rakim.wolfsonmicro.main> <20100224190234.GD25304@core.coreip.homeip.net> <20100224191402.GA8316@rakim.wolfsonmicro.main> <20100224192126.GE25304@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100224192126.GE25304@core.coreip.homeip.net> X-Cookie: You too can wear a nose mitten. 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: 1308 Lines: 28 On Wed, Feb 24, 2010 at 11:21:26AM -0800, Dmitry Torokhov wrote: > On Wed, Feb 24, 2010 at 07:14:03PM +0000, Mark Brown wrote: > > This doesn't help unless you also provide a way for users to obtain a > > struct wm8400. > Why would they need it? Only code that creates instances of wm8400 needs > to know the definition of the sturcture, the rest can simply pass the > pointer around. > I guess there is disconnect between us and I do not see any users of > wm8400_register_regulator() in linux-next... Is there another tree I > could peek at? There are no users in mainline. This would be called by board specific code from the init callback of the wm8400 - you'd need to pass that callback the struct wm8400. In any case, this is clearly an unrelated change to whatever else you were doing to the driver so should be split off into a separate patch, but if this is being changed at all then it'd be much more sensible to change it to use a more modern pattern which completely removes the wm8400_register_regulator() function and just uses platform data. -- 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/