[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7280e507-cafd-f981-88b5-0e7d375e26d4@infradead.org>
Date: Thu, 6 Feb 2020 10:10:28 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Borislav Petkov <bp@...en8.de>,
Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [for-next][PATCH 04/26] bootconfig: Add Extra Boot Config support
On 2/6/20 9:58 AM, Borislav Petkov wrote:
> On Thu, Feb 06, 2020 at 11:41:00PM +0900, Masami Hiramatsu wrote:
>> Oh, you are not the first person asked that :)
(that would be me AFAIK)
>>
>> https://lkml.org/lkml/2019/12/9/563
>>
>> And yes, I think this is important that will useful for most developers
>> and admins. Since the bootconfig already covers kernel and init options,
>> this can be a new standard way to pass args to kernel boot.
>
> Aha, so Steve and you believe this will become the next great thing
> after sliced bread. Sorry but I remain sceptical. :)
old news: some Kconfig symbols are Special & Important. ;)
I agree with you (as I also disagreed with "default y").
> I would've done it differently: have it default 'n' and once it turns
> out that the major distros have enabled it and *actually* use it, *then*
> simply remove the config option. Like we usually do with functionality.
> Not the other way around.
>
> In any case, I've disabled it on my machines and will wait for it
> missing to come back and bite me. :-P
--
~Randy
Powered by blists - more mailing lists