From: Petr Mladek <pmladek@suse.com>
To: Chris Down <chris@chrisdown.name>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-team@fb.com
Subject: Re: [PATCH v5 1/2] printk: Do not delay messages which aren't solicited by any console
Date: Wed, 26 Apr 2023 10:55:58 +0200 [thread overview]
Message-ID: <ZEjnHjBWM0YwS0t5@alley> (raw)
In-Reply-To: <d2bc3639839e232a841bc06c3ca7e8b4d502e412.1682427812.git.chris@chrisdown.name>
On Tue 2023-04-25 14:06:22, Chris Down wrote:
> Boot-delayed printk messages already have this checked up front, and
> it's odd that we don't do the same check for global printk delays, since
> there's no reason to delay if we are not going to emit anything.
>
> Signed-off-by: Chris Down <chris@chrisdown.name>
Great catch!
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2023-04-26 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:06 [PATCH v5 0/2] printk: console: Per-console loglevels Chris Down
2023-04-25 13:06 ` [PATCH v5 1/2] printk: Do not delay messages which aren't solicited by any console Chris Down
2023-04-26 8:55 ` Petr Mladek [this message]
2023-04-25 13:06 ` [PATCH v5 2/2] printk: console: Support console-specific loglevels Chris Down
2023-04-27 13:49 ` Petr Mladek
2023-04-27 15:41 ` John Ogness
2023-05-02 14:28 ` Chris Down
2023-04-30 17:00 ` [PATCH v5 2/2] printk: console: Remove sysrq exception calumlikesapplepie
2023-05-02 9:23 ` Chris Down
2023-05-02 10:27 ` Petr Mladek
2023-05-02 14:26 ` [PATCH v5 2/2] printk: console: Support console-specific loglevels Chris Down
2023-04-28 16:19 ` kernel test robot
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=ZEjnHjBWM0YwS0t5@alley \
--to=pmladek@suse.com \
--cc=chris@chrisdown.name \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@fb.com \
--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®