Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262094AbTKNWLv (ORCPT ); Fri, 14 Nov 2003 17:11:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262458AbTKNWLv (ORCPT ); Fri, 14 Nov 2003 17:11:51 -0500 Received: from fw.osdl.org ([65.172.181.6]:16525 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262094AbTKNWLu (ORCPT ); Fri, 14 Nov 2003 17:11:50 -0500 Date: Fri, 14 Nov 2003 14:07:03 -0800 From: "Randy.Dunlap" To: Chris Friesen Cc: linux-kernel@vger.kernel.org Subject: Re: why no Kconfig in "kernel" subdir? Message-Id: <20031114140703.0ce36149.rddunlap@osdl.org> In-Reply-To: <3FB54A62.6020601@nortelnetworks.com> References: <3FB50B4D.1000300@nortelnetworks.com> <20031114092319.5260bd01.rddunlap@osdl.org> <3FB54A62.6020601@nortelnetworks.com> Organization: OSDL X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 36 On Fri, 14 Nov 2003 16:34:26 -0500 Chris Friesen wrote: | Randy.Dunlap wrote: | | | > I consider PREEMPT and SMP arch-specific, not generic. | | Interesting. Might I ask why? I thought that most of PREEMPT was | pretty arch-neutral. Right, most of it is arch-neutral. It appears that PA-RISC doesn't support PREEMPT: include/asm-parisc/hardirq.h: #ifdef CONFIG_PREEMPT # error CONFIG_PREEMT currently not supported. [complete with typo] and UML doesn't support PREEMPT either. | > Will init/Kconfig do what you want? | | As long as there is some place to put generic options that are | applicable to the system as a whole, then I'm happy. I expect that it's workable. -- ~Randy MOTD: Always include version info. - 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/