From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Jiri Slaby <jirislaby@kernel.org>,
Rajnesh Kanwal <rkanwal@rivosinc.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/serial-console: Document the behavior when the last console= parameter is not used
Date: Fri, 10 Mar 2023 10:54:48 +0900 [thread overview]
Message-ID: <20230310015448.GD1045797@google.com> (raw)
In-Reply-To: <20230308112433.24292-1-pmladek@suse.com>
On (23/03/08 12:24), Petr Mladek wrote:
>
> The console= kernel command-line parameter defines where the kernel
> messages appear. It can be used multiple times to make the kernel log
> visible on more devices.
>
> The ordering of the console= parameters is important. In particular,
> the last one defines which device can be accessed also via /dev/console.
>
> The behavior is more complicated when the last console= parameter is
> ignored by kernel. It might be surprising because it was not intentional.
> The kernel just works this way historically.
>
> There were few attempts to change the behavior. Unfortunately, it can't
> be done because it would break existing users. Document the historical
> behavior at least.
>
> Link: https://lore.kernel.org/r/20170606143149.GB7604@pathway.suse.cz
> Link: https://lore.kernel.org/r/20230213113912.1237943-1-rkanwal@rivosinc.com
> Signed-off-by: Petr Mladek <pmladek@suse.com>
Looks good!
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
prev parent reply other threads:[~2023-03-10 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:24 [PATCH] Documentation/serial-console: Document the behavior when the last console= parameter is not used Petr Mladek
2023-03-09 16:23 ` Greg Kroah-Hartman
2023-03-10 1:54 ` Sergey Senozhatsky [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=20230310015448.GD1045797@google.com \
--to=senozhatsky@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rkanwal@rivosinc.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).