[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200204093302.593cb82e@oasis.local.home>
Date: Tue, 4 Feb 2020 09:33:02 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Tom Zanussi <zanussi@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2] bootconfig: Only load bootconfig if
"config=bootconfig" is on the kernel cmdline (was: bootconfig: Add
"disable_bootconfig" cmdline option to disable bootconfig)
On Tue, 4 Feb 2020 09:25:28 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> As bootconfig is silently added (if the admin does not know where to look
> they may not know it's being loaded). It should be explicitly added to the
> kernel cmdline. The loading of the bootconfig is only done if
> "config=bootconfig" is on the kernel command line. This will let admins know
> that the kernel command line is extended.
I wonder if we need the "config=" part. Would "bootconfig" be
sufficient, or is it better to keep it for documentation purposes.
-- Steve
Powered by blists - more mailing lists