From: Petr Mladek <pmladek@suse.com>
To: Dmitry Safonov <dima@arista.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Safonov <0x7f454c46@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 0/2] printk: Add printk.console_verbose boot param
Date: Fri, 30 Jul 2021 13:01:41 +0200 [thread overview]
Message-ID: <YQPcFQci7p9lE50u@alley> (raw)
In-Reply-To: <20210713011511.215808-1-dima@arista.com>
On Tue 2021-07-13 02:15:09, Dmitry Safonov wrote:
> v1 to v2 Changes:
> - Add printk.console_verbose boot parameter instead of compile-time
> CONFIG_CONSOLE_LOGLEVEL_PANIC (see v1 discussion with Petr)
> - I didn't rename console_verbose() to console_verbose_panic() as
> I need it to be always disabled regardless oops/panic/lockdep.
> - I noticed console_silent() which is unused for long time, remove it.
>
> v1: https://lore.kernel.org/lkml/20210622143350.1105701-1-dima@arista.com/
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: John Ogness <john.ogness@linutronix.de>
> Cc: Petr Mladek <pmladek@suse.com>
> Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
>
> Dmitry Safonov (2):
> printk: Remove console_silent()
> printk: Add printk.console_verbose boot parameter
The patchset is comitted in printk/linux.git, branch
for-5.15-verbose-console.
Best Regards,
Petr
prev parent reply other threads:[~2021-07-30 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 1:15 [PATCH v2 0/2] printk: Add printk.console_verbose boot param Dmitry Safonov
2021-07-13 1:15 ` [PATCH v2 1/2] printk: Remove console_silent() Dmitry Safonov
2021-07-21 14:15 ` Petr Mladek
2021-07-13 1:15 ` [PATCH v2 2/2] printk: Add printk.console_verbose boot parameter Dmitry Safonov
2021-07-21 14:46 ` Petr Mladek
2021-07-26 13:37 ` Dmitry Safonov
2021-07-30 11:00 ` Petr Mladek
2021-07-30 11:01 ` 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=YQPcFQci7p9lE50u@alley \
--to=pmladek@suse.com \
--cc=0x7f454c46@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dima@arista.com \
--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;
as well as URLs for NNTP newsgroup(s).