Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262827AbTENUxT (ORCPT ); Wed, 14 May 2003 16:53:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262834AbTENUxS (ORCPT ); Wed, 14 May 2003 16:53:18 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:62366 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S262827AbTENUxR (ORCPT ); Wed, 14 May 2003 16:53:17 -0400 X-AuthUser: davidel@xmailserver.org Date: Wed, 14 May 2003 14:05:07 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mcafeelabs.com To: "H. Peter Anvin" cc: Linux Kernel Mailing List Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional 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 Content-Length: 849 Lines: 23 On Wed, 14 May 2003, H. Peter Anvin wrote: > Followup to: > By author: Davide Libenzi > In newsgroup: linux.dev.kernel > > > > Not only. Like Ulrich was saying, the config documentation should heavily > > warn the wild config guy about the consequences of a 'NO' over there. > > > > How about creating a master option like we have for experimental? > Something like "Allow removal of essential components?" (CONFIG_EMBEDDED) I'd agree. Not showing them at all for std configurations is even better. - Davide - 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/