Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751970AbXB1IMb (ORCPT ); Wed, 28 Feb 2007 03:12:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751735AbXB1IMb (ORCPT ); Wed, 28 Feb 2007 03:12:31 -0500 Received: from gate.crashing.org ([63.228.1.57]:60116 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751278AbXB1IMa (ORCPT ); Wed, 28 Feb 2007 03:12:30 -0500 Subject: Re: [RFC] killing the NR_IRQS arrays. From: Benjamin Herrenschmidt To: "Eric W. Biederman" Cc: Arnd Bergmann , Arjan van de Ven , Ingo Molnar , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Andi Kleen , Alan Cox , Thomas Gleixner In-Reply-To: References: <1171844753.5644.174.camel@localhost.localdomain> <200702280141.51420.arnd@arndb.de> Content-Type: text/plain Date: Wed, 28 Feb 2007 09:09:44 +0100 Message-Id: <1172650184.11949.96.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1012 Lines: 24 > What I really object to is not the irq numbers. As an arbitrary number > does not impose limits. What I object to is drivers that can't handle the > full range of numbers, and the limits imposed upon those numbers when > you require them to be indexes into an array. > > For talking to user space I expect we will have numbers for a long time > to come yet. I wouldn't bother too much about going into bus specific bits like irq_request(dev, ...). Well, actually, I _do_ think it's a good thing to pass the struct device to irq_request but that's a different issue completely. I think bus types should provide bus specific helpers to obtain the struct irq *'s for a given device on that bus, but the API for requesting/freeing them shall remain generic. Ben. - 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/