bootconfig: Default BOOT_CONFIG_FORCE to y if BOOT_CONFIG_EMBED
authorPaul E. McKenney <paulmck@kernel.org>
Tue, 21 Feb 2023 23:27:49 +0000 (08:27 +0900)
committerMasami Hiramatsu (Google) <mhiramat@kernel.org>
Tue, 21 Feb 2023 23:27:49 +0000 (08:27 +0900)
When a kernel is built with CONFIG_BOOT_CONFIG_EMBED=y, the intention
will normally be to unconditionally provide the specified kernel-boot
arguments to the kernel, as opposed to requiring a separately provided
bootconfig parameter.  Therefore, make the BOOT_CONFIG_FORCE Kconfig
option default to y in kernels built with CONFIG_BOOT_CONFIG_EMBED=y.

The old semantics may be obtained by manually overriding this default.

Link: https://lore.kernel.org/all/20230107162202.GA4028633@paulmck-ThinkPad-P17-Gen-1/
Suggested-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
init/Kconfig

index 04f0c5bb9e150a86f836db83255c8f775d755cfe..53bb993e54210f9dcceab8b6e053d187844280ac 100644 (file)
@@ -1383,6 +1383,7 @@ config BOOT_CONFIG
 config BOOT_CONFIG_FORCE
        bool "Force unconditional bootconfig processing"
        depends on BOOT_CONFIG
+       default y if BOOT_CONFIG_EMBED
        help
          With this Kconfig option set, BOOT_CONFIG processing is carried
          out even when the "bootconfig" kernel-boot parameter is omitted.