From: Petr Mladek <pmladek@suse.com>
To: Andre Kalb <andre.kalb@sma.de>
Cc: senozhatsky@chromium.org, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH v3] printk: Set console_set_on_cmdline=1 when __add_preferred_console() is called with user_specified == true
Date: Mon, 21 Feb 2022 16:49:16 +0100 [thread overview]
Message-ID: <YhO0fBJLn4hW2LyC@alley> (raw)
In-Reply-To: <YgzU4ho8l6XapyG2@pc6682>
On Wed 2022-02-16 11:41:38, Andre Kalb wrote:
> From: Andre Kalb <andre.kalb@sma.de>
>
> In case of using console="" or console=null
> set console_set_on_cmdline=1 to disable "stdout-path" node from DT.
>
> We basically need to set it every time when __add_preferred_console()
> is called with parameter 'user_specified' set.
> Therefore we can move setting it into a helper function that is
> called from __add_preferred_console().
>
> Suggested-by: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Andre Kalb <andre.kalb@sma.de>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
The patch is comitted in printk/linux.git, branch for-5.18.
Best Regards,
Petr
prev parent reply other threads:[~2022-02-21 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:00 [PATCH] printk: Set console_set_on_cmdline=1 when using console="" or console=null Andre Kalb
2022-02-08 15:55 ` 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 [this message]
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=YhO0fBJLn4hW2LyC@alley \
--to=pmladek@suse.com \
--cc=andre.kalb@sma.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®