Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945943AbXBPPuy (ORCPT ); Fri, 16 Feb 2007 10:50:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1945947AbXBPPuy (ORCPT ); Fri, 16 Feb 2007 10:50:54 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:55904 "EHLO ebiederm.dsl.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1945943AbXBPPux (ORCPT ); Fri, 16 Feb 2007 10:50:53 -0500 From: ebiederm@xmission.com (Eric W. Biederman) To: Ingo Molnar Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Andi Kleen , Benjamin Herrenschmidt , Alan Cox Subject: Re: [RFC] killing the NR_IRQS arrays. References: <20070216124117.GB4218@elte.hu> Date: Fri, 16 Feb 2007 08:49:43 -0700 In-Reply-To: <20070216124117.GB4218@elte.hu> (Ingo Molnar's message of "Fri, 16 Feb 2007 13:41:17 +0100") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) 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 Content-Length: 809 Lines: 25 Ingo Molnar writes: > > or am i missing something fundamental? One piece. At the driver level this not a big scary change. This is just a change with widespread effect. It should be no worse than enabling a very revealing new compiler warning. Every fix should be purely mechanical. There should be no need at all to think to get it right (unless things are broken today and we just don't see it.). Yes typo's and the like will happen. There will be issues. But 99% of them will be the code doesn't compile, for an obvious reason. Eric - 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/