From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 31B332FA for ; Wed, 21 May 2014 08:53:33 +0000 (UTC) Received: from arkanian.console-pimps.org (arkanian.console-pimps.org [212.110.184.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 802BE1F80A for ; Wed, 21 May 2014 08:53:31 +0000 (UTC) Date: Wed, 21 May 2014 09:53:28 +0100 From: Matt Fleming To: Dan Williams Message-ID: <20140521085328.GJ4798@console-pimps.org> References: <20140516125611.06633446@notabene.brown> <537628ED.1020208@fb.com> <20140521182552.2ed57ad7@notabene.brown> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] [nomination] Move Fast and Oops Things List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 21 May, at 01:36:55AM, Dan Williams wrote: > > My straw man is something like the following for driver "foo" > > if (gatekeeper_foo_new_awesome_sauce) > do_new_thing(); > > Where setting gatekeeper_foo_new_awesome_sauce taints the kernel and > warns that there is no guarantee of this functionality being present > in the same form or at all going forward. This kind of thing is done all the time for web developemnt - I think it's given the name "feature bit". It makes sense when you control the execution environment, like a web server, and if things explode you can detect that on the web server end, and not necessarily require your user to report the problem. It also makes a lot of sense for continuous deployment, where the master branch is always the branch used in production. When a user needs to actively enable this feature and report problems it's just like another CONFIG_* option, and I'm not sure that's an improvement. -- Matt Fleming, Intel Open Source Technology Center