Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262874AbTE2Vwv (ORCPT ); Thu, 29 May 2003 17:52:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262934AbTE2Vwr (ORCPT ); Thu, 29 May 2003 17:52:47 -0400 Received: from modemcable204.207-203-24.mtl.mc.videotron.ca ([24.203.207.204]:21633 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id S262874AbTE2VwR (ORCPT ); Thu, 29 May 2003 17:52:17 -0400 Date: Thu, 29 May 2003 17:55:15 -0400 (EDT) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: "Nguyen, Tom L" cc: Jeff Garzik , "Nakajima, Jun" , "" Subject: RE: RFC Proposal to enable MSI support in Linux kernel In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 May 2003, Nguyen, Tom L wrote: > I am working on an updated patch to 2.5.70 to incorporate the comments > from you and Jeff Garzik. Regarding the variable renaming of irq, I am > open to any suggestions. Please make a recommendation and I will > incorporate it into the next update. Well essentially, if the function is being passed a vector, lets call the parameter 'vector', right now you have to look at the code paths careful to determine wether it's an irq number or a vector masquerading as an irq number. > Regarding platform_legacy_irq, I have not seen an edge-triggered > interrupt failure caused by platform_legacy_irq. So we can go with Jeff's suggestion there and remove the unecessary check for wether to assign level or edge? Zwane -- function.linuxpower.ca - 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/