All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: hujinfei <3288824963@qq.com>
Cc: linux-doc@vger.kernel.org, senozhatsky@chromium.org,
	qujingling@huawei.com, zhangjiaji1@huawei.com,
	xushuangxing@huawei.com, rostedt@goodmis.org,
	john.ogness@linutronix.de, hujinfei3@huawei.com
Subject: Re: [PATCH] Documentation: printk: warn about lockups from excessive use
Date: Tue, 10 Mar 2026 16:31:44 +0100	[thread overview]
Message-ID: <abA5YDfTuU7cuq2a@pathway.suse.cz> (raw)
In-Reply-To: <tencent_6D5FBEBE0E2FDACC93E50D0893497F676407@qq.com>

On Thu 2026-03-05 14:41:40, hujinfei wrote:
> From: hujinfei <hujinfei3@huawei.com>
> 
> Add a section 'Avoiding lockups from excessive printk() use' to
> printk-basics.rst, explaining the risk of calling printk() in hot paths
> with slow consoles and suggesting alternatives like ratelimited printing,
> tracepoints, nbcon, and log level filtering.
> 
> Signed-off-by: hujinfei <hujinfei3@huawei.com>

Looks good to me.

Reviewed-by: Petr Mladek <pmladek@suse.com>

Best Regards,
Petr

PS: I am going to wait few more days for a potential feedback and
    will push it to printk/linux.git if nobody complains.

  parent reply	other threads:[~2026-03-10 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  6:41 [PATCH] Documentation: printk: warn about lockups from excessive use hujinfei
2026-03-05 23:25 ` Randy Dunlap
2026-03-10 15:31 ` Petr Mladek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-04 14:40 hujinfei
2026-03-04 21:18 ` Randy Dunlap
2026-03-05  1:49 ` Steven Rostedt
2026-03-13 10:27 ` John Ogness

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=abA5YDfTuU7cuq2a@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=3288824963@qq.com \
    --cc=hujinfei3@huawei.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=qujingling@huawei.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=xushuangxing@huawei.com \
    --cc=zhangjiaji1@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.