From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753908AbaJTVma (ORCPT ); Mon, 20 Oct 2014 17:42:30 -0400 Received: from mail-lb0-f175.google.com ([209.85.217.175]:60553 "EHLO mail-lb0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751704AbaJTVm3 (ORCPT ); Mon, 20 Oct 2014 17:42:29 -0400 MIME-Version: 1.0 In-Reply-To: <20141020144117.b75967da82113b1851e2596e@linux-foundation.org> References: <5c6381879bea68aebb13530442f1cf8a052be97f.1411958379.git.luto@amacapital.net> <542B4DA3.5080105@gmail.com> <542B519B.6010001@landley.net> <542B5E44.40303@gmail.com> <542B7200.6030902@landley.net> <20141001180510.GA28540@cloud> <20141014140052.2f114c158ffe6cd953020f1c@linux-foundation.org> <20141020210155.GD29486@jtriplet-mobl1> <20141020142836.fcea4aa8dd7bb5cfe9ede423@linux-foundation.org> <20141020144117.b75967da82113b1851e2596e@linux-foundation.org> From: Andy Lutomirski Date: Mon, 20 Oct 2014 14:42:07 -0700 Message-ID: Subject: Re: [PATCH v5] init: Disable defaults if init= fails To: Andrew Morton Cc: Josh Triplett , Rob Landley , Frank Rowand , "linux-kernel@vger.kernel.org" , Chuck Ebbert , Randy Dunlap , Shuah Khan Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 20, 2014 at 2:41 PM, Andrew Morton wrote: > On Mon, 20 Oct 2014 14:34:14 -0700 Andy Lutomirski wrote: > >> On Mon, Oct 20, 2014 at 2:28 PM, Andrew Morton >> wrote: >> > On Mon, 20 Oct 2014 14:01:55 -0700 Josh Triplett wrote: >> > >> >> > IOW, the no-fallback behavior is easy to implement, easy to >> >> > understand, and has extremely predictable behavior. The fallback >> >> > behavior is more user friendly if you consider having a chance of >> >> > booting to something useful if you typo your init= option (but also a >> >> > chance of booting to something actively undesirable). >> >> >> >> Here's an alternative proposal: how about we change the default >> >> *without* a Kconfig option, see if anyone screams, and if they do, we >> >> add that code back in under a Kconfig option as in your current patch? >> >> >> >> Would that make your Kconfig senses stop tingling, Andrew? :) >> > >> > Mumble. I suppose we can run with it as-is: at least the config option >> > is there to allow people to repair any damage easily. >> > >> > However we don't have any way of remembering to remove the config >> > option later coz someone removed feature-removal-schedule.txt, which >> > was a useful feature. >> >> Does -mm have a next+1 section? If so, you could queue it up now :) > > Yes, I can do that. I add little notes-to-self in the series file to > remember such things. Should I send you a patch, or do you want to write it yourself? --Andy -- Andy Lutomirski AMA Capital Management, LLC