From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from terminus.zytor.com ([198.137.202.10]:54831 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752024Ab1GaA3z (ORCPT ); Sat, 30 Jul 2011 20:29:55 -0400 Message-ID: <4E34A1E4.8040103@zytor.com> Date: Sat, 30 Jul 2011 17:29:24 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 Subject: Re: [PATCH 2/2] Enable 'make CONFIG_FOO=y oldconfig' References: <1312067499.22074.59.camel@i7.infradead.org> <1312067670.22074.61.camel@i7.infradead.org> <4E34998D.8060806@zytor.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Arnaud Lacombe Cc: David Woodhouse , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org On 07/30/2011 05:05 PM, Arnaud Lacombe wrote: >> >> Why???? >> > Because kconfig might not be ran exclusively from a fully controlled > and restricted environment ? Not to mention that it is used by other > people than the linux kernel folks. > I'm sorry, but whitelisting specific options is an absolutely idiotic way to deal with that. The options use a specific namespace (CONFIG_*), and only allowing some options to be set on the command line, but not others, is a serious violation of the principle of least surprise. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.