public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Kalb <svc.sw.rte.linux@sma.de>
To: Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH] printk: Set console_set_on_cmdline=1 when using console="" or console=null
Date: Fri, 28 Jan 2022 00:00:52 +0100	[thread overview]
Message-ID: <YfMkJKUuGBwyT611@pc6682> (raw)

In case of using console="" or console=null set console_set_on_cmdline=1
to disable chosen{ "stdout-path" } node from devicetree.

To jump out from drivers/of/base.c, line 2087 of_console_check function
with false.

Signed-off-by: Andre Kalb <andre.kalb@sma.de>
---
 kernel/printk/printk.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 82abfaf3c2aa..df5ab35b8af2 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2385,6 +2385,7 @@ static int __init console_setup(char *str)
 	 */
 	if (str[0] == 0 || strcmp(str, "null") == 0) {
 		__add_preferred_console("ttynull", 0, NULL, NULL, true);
+		console_set_on_cmdline = 1;
 		return 1;
 	}
 
-- 
2.31.1


             reply	other threads:[~2022-01-27 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:00 Andre Kalb [this message]
2022-02-08 15:55 ` [PATCH] printk: Set console_set_on_cmdline=1 when using console="" or console=null Petr Mladek
2022-02-14 13:21   ` [PATCH v2] printk: Set console_set_on_cmdline=1 when __add_preferred_console() is called with user_specified == true Andre Kalb
2022-02-15  3:15     ` Sergey Senozhatsky
2022-02-15 17:58       ` Petr Mladek
2022-02-15 18:10     ` Petr Mladek
2022-02-16  3:18       ` Sergey Senozhatsky
2022-02-16 10:41         ` [PATCH v3] " Andre Kalb
2022-02-21 15:49           ` Petr Mladek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YfMkJKUuGBwyT611@pc6682 \
    --to=svc.sw.rte.linux@sma.de \
    --cc=andre.kalb@sma.de \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox