From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: [patch 2.6.25-git] i2c_adapters: return -Errno not -1 Date: Sun, 11 May 2008 00:32:53 -0700 Message-ID: <200805110032.54247.david-b@pacbell.net> References: <200805012046.07885.david-b@pacbell.net> <20080510201825.489198d2@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080510201825.489198d2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Errors-To: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org To: Jean Delvare Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Saturday 10 May 2008, Jean Delvare wrote: > I am in the process of reviewing and testing this patch. I think it > would help me if you could list your error value choices for the common > error conditions of I2C and SMBus controllers (bus busy, arbitration > lost, transaction timeout, etc.) With such a list I could check the > different drivers for consistency, and maybe this could even become > documentation for future driver authors. Yeah, I'll write something up. Agreed that would be handy ... and since not all the fault codes indicate errors (losing arbitration, for example), it's important to agree on codes where we think that drivers should eventually be able to kick in recovery strategies. - Dave _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c