@@ -228,10 +229,8 @@ static void __init parse_dtb(void)}pr_err("No DTB passed to the kernel\n");-#ifdef CONFIG_CMDLINE_FORCE-strlcpy(boot_command_line,CONFIG_CMDLINE,COMMAND_LINE_SIZE);+cmdline_build(boot_command_line,NULL,COMMAND_LINE_SIZE);pr_info("Forcing kernel command line to: %s\n",boot_command_line);
Shouldn't that message become conditional in some way?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
@@ -228,10 +229,8 @@ static void __init parse_dtb(void)}pr_err("No DTB passed to the kernel\n");-#ifdef CONFIG_CMDLINE_FORCE-strlcpy(boot_command_line,CONFIG_CMDLINE,COMMAND_LINE_SIZE);+cmdline_build(boot_command_line,NULL,COMMAND_LINE_SIZE);pr_info("Forcing kernel command line to: %s\n",boot_command_line);
Shouldn't that message become conditional in some way?
You are right, I did something similar on ARM but looks like I missed it on RISCV.
Christophe
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
@@ -228,10 +229,8 @@ static void __init parse_dtb(void)}pr_err("No DTB passed to the kernel\n");-#ifdef CONFIG_CMDLINE_FORCE-strlcpy(boot_command_line,CONFIG_CMDLINE,COMMAND_LINE_SIZE);+cmdline_build(boot_command_line,NULL,COMMAND_LINE_SIZE);pr_info("Forcing kernel command line to: %s\n",boot_command_line);
Shouldn't that message become conditional in some way?
You are right, I did something similar on ARM but looks like I missed it on RISCV.
How is this hunk even useful? Under what conditions can you boot
without a DTB? Even with a built-in DTB, the DT cmdline handling would
be called.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
@@ -228,10 +229,8 @@ static void __init parse_dtb(void)}pr_err("No DTB passed to the kernel\n");-#ifdef CONFIG_CMDLINE_FORCE-strlcpy(boot_command_line,CONFIG_CMDLINE,COMMAND_LINE_SIZE);+cmdline_build(boot_command_line,NULL,COMMAND_LINE_SIZE);pr_info("Forcing kernel command line to: %s\n",boot_command_line);
Shouldn't that message become conditional in some way?
You are right, I did something similar on ARM but looks like I missed
it on RISCV.
How is this hunk even useful? Under what conditions can you boot
without a DTB? Even with a built-in DTB, the DT cmdline handling would
be called.
Rob
@@ -228,10 +229,8 @@ static void __init parse_dtb(void)}pr_err("No DTB passed to the kernel\n");-#ifdef CONFIG_CMDLINE_FORCE-strlcpy(boot_command_line,CONFIG_CMDLINE,COMMAND_LINE_SIZE);+cmdline_build(boot_command_line,NULL,COMMAND_LINE_SIZE);pr_info("Forcing kernel command line to: %s\n",boot_command_line);
Shouldn't that message become conditional in some way?
You are right, I did something similar on ARM but looks like I missed it on RISCV.
How is this hunk even useful? Under what conditions can you boot
without a DTB? Even with a built-in DTB, the DT cmdline handling would
be called.
Don't know, I wanted to keep as is today.
Do you think the hunk should be completely removed ?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel