[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200219112651.ea5d46978b79a33566660d8f@kernel.org>
Date: Wed, 19 Feb 2020 11:26:51 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.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 Tue, 18 Feb 2020 20:38:50 +0100
Borislav Petkov <bp@...en8.de> wrote:
> On Tue, Feb 18, 2020 at 12:57:48PM -0500, Steven Rostedt wrote:
> > OK, what if we put it as default 'n' but we still check if "bootconfig"
> > is on the command line. And if it is, we warn with something like:
> >
> > #ifndef CONFIG_BOOTCONFIG
> > pr_err("WARNING: 'bootconfig' found on the kernel command line but CONFIG_BOOTCONFIG is not set in this kernel\n");
> > #endif
>
> Sure, makes sense to me. And all the code that requires it, can simply
> select BOOTCONFIG.
OK, so I'll update it.
Thanks!
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists