[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWEoBrFRhmLEByhDCasuMrbGS4PreRivYRApdsME7x2AA@mail.gmail.com>
Date: Thu, 27 Feb 2020 10:22:00 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Borislav Petkov <bp@...en8.de>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2 1/8] bootconfig: Set CONFIG_BOOT_CONFIG=n by default
Hi Hiramatsu-san,
On Thu, Feb 20, 2020 at 1:18 PM Masami Hiramatsu <mhiramat@...nel.org> wrote:
> Set CONFIG_BOOT_CONFIG=n by default. This also warns
> user if CONFIG_BOOT_CONFIG=n but "bootconfig" is given
> in the kernel command line.
>
> Suggested-by: Steven Rostedt <rostedt@...dmis.org>
> Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
Thanks for your patch!
> --- a/init/main.c
> +++ b/init/main.c
> @@ -418,6 +418,14 @@ static void __init setup_boot_config(const char *cmdline)
> }
> #else
> #define setup_boot_config(cmdline) do { } while (0)
> +
> +static int __init warn_bootconfig(char *str)
> +{
> + pr_warn("WARNING: 'bootconfig' found on the kernel command line but CONFIG_BOOTCONFIG is not set.\n");
> + return 0;
> +}
> +early_param("bootconfig", warn_bootconfig);
Yeah, let's increases kernel size for the people who don't want to jump
on the bootconfig wagon :-(
Is this really needed?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists