From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [i2c] [PATCH 19 3/5] Clean up error returns Date: Tue, 22 Jan 2008 10:04:44 +1100 Message-ID: <1200956684.6807.14.camel@pasglop> References: <20080112024737.7023.61680.stgit@terra.home> <20080112024743.7023.23630.stgit@terra.home> <20080120120730.06dd8a7f@hyperion.delvare> <9e4733910801200718q7304bc29q38e67580613189e4@mail.gmail.com> <9e4733910801200739x502d5407x85f0d950ace80bee@mail.gmail.com> <20080121171025.524dc465@hyperion.delvare> Reply-To: benh@kernel.crashing.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080121171025.524dc465@hyperion.delvare> Sender: linux-kernel-owner@vger.kernel.org To: Jean Delvare Cc: Jon Smirl , i2c@lm-sensors.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Mon, 2008-01-21 at 17:10 +0100, Jean Delvare wrote: > Hi Jon, > > On Sun, 20 Jan 2008 10:39:43 -0500, Jon Smirl wrote: > > Here' s a version with the compares to zero switched to NO_IRQ. If I > > understand how NO_IRQ works it is the correct change. My understanding > > is that under ppc IRQ zero was legal and NO_IRQ was -1. But then the > > whole kernel switched to NO_IRQ = zero. Powerpc updated to NO_IRQ=0 > > and used virtual IRQs to move a physical IRQ 0 to another IRQ number. > > ppc was not changed. This driver does not appear to have been updated > > to track this global change since it didn't initially use the NO_IRQ > > define everywhere. > > As I have already applied the part of this patch that preserves error > values in error paths, can you please send an incremental patch that > only fixes the IRQ issues? These are separate issues so it's better to > have separate patches anyway. To be clear, nowadays, checking against 0 is correct unless you intend the driver to work with arch/ppc (which we'll deprecate soon). Ben.