From: Greg KH <gregkh@linuxfoundation.org>
To: Fushuai Wang <fushuai.wang@linux.dev>
Cc: broonie@kernel.org, andy.shevchenko@gmail.com,
asrinivasan@oss.tenstorrent.com, jackzxcui1989@163.com,
jirislaby@kernel.org, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
osama.abdelkader@gmail.com, wangfushuai@baidu.com
Subject: Re: [PATCH v2] Revert "serial: 8250: Clear CON_PRINTBUFFER on port re-registration"
Date: Wed, 29 Jul 2026 15:11:39 +0200 [thread overview]
Message-ID: <2026072927-lather-print-3f5f@gregkh> (raw)
In-Reply-To: <20260729112605.11764-1-fushuai.wang@linux.dev>
On Wed, Jul 29, 2026 at 07:26:05PM +0800, Fushuai Wang wrote:
> > > From: Fushuai Wang <wangfushuai@baidu.com>
> > >
> > > This reverts commit d338ab1d90603f875c4f7ed223406535378173a5.
> > >
> > > uart_console() only indicates that the port is selected as the console.
> > > It does not mean that the console has already been registered or has
> > > printed the buffered messages.
> >
> > The multi-system boot regression this fixes is still present in -next.
>
> Hi, Greg
>
> Just a ping.
>
> Mark has confirmed that the regression is still present in -next.
> Could you please take a look and consider applying it to tty/tty-testing
> and tty/tty-next?
Will do, working on my patch queue right now...
prev parent reply other threads:[~2026-07-29 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:31 [PATCH v2] Revert "serial: 8250: Clear CON_PRINTBUFFER on port re-registration" Fushuai Wang
2026-07-29 10:21 ` Mark Brown
2026-07-29 11:26 ` Fushuai Wang
2026-07-29 13:11 ` Greg KH [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=2026072927-lather-print-3f5f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=asrinivasan@oss.tenstorrent.com \
--cc=broonie@kernel.org \
--cc=fushuai.wang@linux.dev \
--cc=jackzxcui1989@163.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=osama.abdelkader@gmail.com \
--cc=wangfushuai@baidu.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.