From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: removing set_clientdata(NULL) Date: Mon, 29 Mar 2010 18:43:55 +0200 Message-ID: <20100329184355.6b23cd54@hyperion.delvare> References: <20100327121558.GA5880@pengutronix.de> <20100329162812.548d131b@hyperion.delvare> <20100329150956.GB6717@pengutronix.de> <20100329172734.7cd7341d@hyperion.delvare> <20100329154910.GE13239@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100329154910.GE13239-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Brown Cc: Wolfram Sang , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Mon, 29 Mar 2010 16:49:10 +0100, Mark Brown wrote: > On Mon, Mar 29, 2010 at 05:27:34PM +0200, Jean Delvare wrote: > > On Mon, 29 Mar 2010 17:09:56 +0200, Wolfram Sang wrote: > > > > - shall this better go via the i2c-tree? > > > This seems simpler, yes. I don't think subsystem or driver maintainers > > need to be bothered with what is really only a cleanup. > > What about those subsystems where the maintainers applied the patch from > the first round (adding the explicit set to NULL where it had been > missing)? I don't think we can ask them to revert, as they won't like it (except for the few of working with quilt). So the best way is to let them push the change upstream and amend it right after. Not ideal, but I can't propose anything better (short of a time travelling machine, that is.) -- Jean Delvare