Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756033AbZAAUiN (ORCPT ); Thu, 1 Jan 2009 15:38:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751859AbZAAUh7 (ORCPT ); Thu, 1 Jan 2009 15:37:59 -0500 Received: from smtp.tal.de ([81.92.1.5]:49580 "EHLO smtp.tal.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbZAAUh7 (ORCPT ); Thu, 1 Jan 2009 15:37:59 -0500 From: ib@wupperonline.de (Ingo Brueckl) Date: Thu, 01 Jan 2009 21:37:00 +0100 Subject: x86 (Linux Tiny): configure out support for some processors X-Mailer: blueMail 1.4 (SlipDoor 2.2) Message-ID: <495d2974@wupperonline.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII To: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 548 Lines: 11 Is there any reason why CONFIG_PROCESSOR_SELECT is limited to EMBEDDED only? In my desktop pc is one specific cpu only, so I do not need support for the other processors. Unfortunately, I have no chance to disable the other ones. As it is already configurable, why not giving this option to everyone? -- 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/