From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Imre Kaloz <kaloz@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH v2] MIPS: SGI-IP27: print the NMI dump on an nbcon console
Date: Fri, 2 Oct 2026 11:30:59 +0200 [thread overview]
Message-ID: <2026100248-scone-rink-e1a3@gregkh> (raw)
In-Reply-To: <ar9c6LwwwRbKW4fp@pathway.suse.cz>
On Fri, Oct 02, 2026 at 09:27:36AM +0200, Petr Mladek wrote:
> On Thu 2026-10-01 21:19:38, Imre Kaloz wrote:
> > Since the 8250 console became nbcon, printk() in nmi_dump() only queues
> > records for a printer thread that never runs, as no CPU leaves the NMI
> > handler. Print from an emergency section and flush pending records
> > before the hub reset.
> >
> > Fixes: d3539347022a ("serial: 8250: Switch to nbcon console, take 2")
> > Signed-off-by: Imre Kaloz <kaloz@kernel.org>
>
> Looks good to me:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
> I assume that it would go via mips or drivers tree.
> Please, let me know if you would prefer to push it via printk tree.
Should probably go through a mips tree to resolve the conflicts.
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-02 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 19:19 [PATCH v2] MIPS: SGI-IP27: print the NMI dump on an nbcon console Imre Kaloz
2026-10-01 19:55 ` John Ogness
2026-10-02 7:27 ` Petr Mladek
2026-10-02 9:30 ` Greg Kroah-Hartman [this message]
2026-10-02 9:13 ` sashiko-bot
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=2026100248-scone-rink-e1a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kaloz@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tsbogend@alpha.franken.de \
/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.