summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorMasami Hiramatsu (Google) <mhiramat@kernel.org>2023-02-28 04:01:42 +0300
committerMasami Hiramatsu (Google) <mhiramat@kernel.org>2023-03-22 16:21:43 +0300
commitcaa0708a81d6a2217c942959ef40d515ec1d3108 (patch)
tree03e67896b40c7be6cfb911a4e7b287a9cd58c2c2 /scripts
parentb69245126a48e50882021180fa5d264dc7149ccc (diff)
downloadlinux-caa0708a81d6a2217c942959ef40d515ec1d3108.tar.xz
bootconfig: Change message if no bootconfig with CONFIG_BOOT_CONFIG_FORCE=y
Change no bootconfig data error message if user do not specify 'bootconfig' option but CONFIG_BOOT_CONFIG_FORCE=y. With CONFIG_BOOT_CONFIG_FORCE=y, the kernel proceeds bootconfig check even if user does not specify 'bootconfig' option. So the current error message is confusing. Let's show just an information message to notice skipping the bootconfig in that case. Link: https://lore.kernel.org/all/167754610254.318944.16848412476667893329.stgit@devnote2/ Fixes: b743852ccc1d ("Allow forcing unconditional bootconfig processing") Reported-by: Geert Uytterhoeven <geert@linux-m68k.org> Link: https://lore.kernel.org/all/CAMuHMdV9jJvE2y8gY5V_CxidUikCf5515QMZHzTA3rRGEOj6=w@mail.gmail.com/ Suggested-by: Paul E. McKenney <paulmck@kernel.org> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Tested-by: Paul E. McKenney <paulmck@kernel.org> Acked-by: Mukesh Ojha <quic_mojha@quicinc.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions