From: Breno Leitao <leitao@debian.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Russell King <linux@armlinux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
John Ogness <john.ogness@linutronix.de>,
Toshiyuki Sato <fj6611ie@aa.jp.fujitsu.com>,
kernel-team@meta.com
Subject: Re: [PATCH] serial: amba-pl011: touch the watchdogs in write_atomic()
Date: Thu, 5 Nov 2026 02:42:39 -0800 [thread overview]
Message-ID: <auxdWQsUW06CpDGX@gmail.com> (raw)
In-Reply-To: <auxcc43USXjFxBeI@pathway.suse.cz>
On Thu, Nov 05, 2026 at 11:37:39AM +0100, Petr Mladek wrote:
> > --- a/drivers/tty/serial/amba-pl011.c
> > +++ b/drivers/tty/serial/amba-pl011.c
> > @@ -41,6 +41,7 @@
> > #include <linux/sizes.h>
> > #include <linux/io.h>
> > #include <linux/acpi.h>
> > +#include <linux/nmi.h>
> >
> > #define UART_NR 14
> >
> > @@ -2734,6 +2735,9 @@ pl011_console_write_atomic(struct console *co, struct nbcon_write_context *wctxt
> > struct uart_amba_port *uap = amba_ports[co->index];
> > unsigned int old_cr = 0;
> >
> > + /* An atomic flush may print a long backlog with IRQs disabled. */
> > + touch_nmi_watchdog();
> > +
>
> I would personally touch the watchdog at the end before returning from
> the function because it still could spend some non-trivial time
> in this function.
Ack, let me move it as you've just suggested, given I have no preference
at all. I will respin it soon.
Thanks for the review,
--breno
prev parent reply other threads:[~2026-11-05 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 10:35 [PATCH] serial: amba-pl011: touch the watchdogs in write_atomic() Breno Leitao
2026-11-04 11:02 ` sashiko-bot
2026-11-04 11:22 ` John Ogness
2026-11-05 10:37 ` Petr Mladek
2026-11-05 10:42 ` Breno Leitao [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=auxdWQsUW06CpDGX@gmail.com \
--to=leitao@debian.org \
--cc=fj6611ie@aa.jp.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=pmladek@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox