From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH 2/3] i2c/pxa: only define 'blue_murder'-function if DEBUG is #defined Date: Sun, 28 Feb 2010 15:55:02 +0000 Message-ID: <20100228155502.GB16745@n2100.arm.linux.org.uk> References: <20100224110044.GB15181@pengutronix.de> <1267009306-17227-2-git-send-email-u.kleine-koenig@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <1267009306-17227-2-git-send-email-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Ben Dooks , Pavel Machek , Roel Kluin , Wolfram Sang , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Wed, Feb 24, 2010 at 12:01:45PM +0100, Uwe Kleine-K=F6nig wrote: > From: Wolfram Sang >=20 > This talkative function is also called on timeouts. As timeouts can > happen on regular writes to EEPROMs (no error case), this creates fal= se > positives. Giving lots of details is interesting only for developers > anyhow, so just use the function if DEBUG is #defined. Are you sure this is safe? If you time out the write before it complet= es, how do you know if the write was successful? I don't think this is "no error code" nor "false positive". If the tim= eout is too short for your EEPROMs, then the timeout needs to be increased.