From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wander Lairson Costa <wander@redhat.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Johan Hovold" <johan@kernel.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Lukas Wunner" <lukas@wunner.de>, "Pali Rohár" <pali@kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
rostedt@goodmis.org, senozhatsky@chromium.org,
andre.goddard@gmail.com, sudipm.mukherjee@gmail.com,
David.Laight@aculab.com, jonathanh@nvidia.com,
phil@raspberrypi.com
Subject: Re: [PATCH v4 0/5] tty/8250: Use fifo in 8250 console driver
Date: Wed, 16 Mar 2022 18:13:19 +0200 [thread overview]
Message-ID: <YjIMn/cBf7STIxBU@smile.fi.intel.com> (raw)
In-Reply-To: <20220316143646.13301-1-wander@redhat.com>
On Wed, Mar 16, 2022 at 11:36:39AM -0300, Wander Lairson Costa wrote:
> This version fixes the bugs reported in version v3. The first patch
> is the same patch of v3 as is. The following commits fix the issues in the
> original patch. For details, please check the commit log of each patch.
>
> I tested these patches in the following systems:
>
> * IBM X3550 M3
> * HP ProLiant DL380 Gen9
> * HP ProLiant BL480c G1
> * Dell PowerEdge R910
> * Cisco UCSC-C220-M3S
>
> I cc everybody that reported problems with the previous version of this
> patch so they can retest and confirm their systems work flawlessly.
I have got this only message and I don't see any good changelog what has
been done between v3 and v4.
> Wander Lairson Costa (5):
> serial/8250: Use fifo in 8250 console driver
> serial/8250: Use the cache value of the FCR register
> serial/8250: Use tx_loadsz as the transmitter fifo size
> serial/8250: exclude BCM283x from console_fifo_write
> serial/8250: Only use fifo after the port is initialized in
> console_write
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-16 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 14:36 [PATCH v4 0/5] tty/8250: Use fifo in 8250 console driver Wander Lairson Costa
2022-03-16 14:36 ` [PATCH v4 1/5] serial/8250: " Wander Lairson Costa
2022-03-16 15:27 ` David Laight
2022-03-17 12:27 ` Wander Costa
2022-03-16 14:36 ` [PATCH v4 2/5] serial/8250: Use the cache value of the FCR register Wander Lairson Costa
2022-03-17 8:29 ` Ilpo Järvinen
2022-03-17 12:03 ` Wander Costa
2022-03-16 14:36 ` [PATCH v4 3/5] serial/8250: Use tx_loadsz as the transmitter fifo size Wander Lairson Costa
2022-03-16 14:36 ` [PATCH v4 4/5] serial/8250: exclude BCM283x from console_fifo_write Wander Lairson Costa
2022-03-16 14:36 ` [PATCH v4 5/5] serial/8250: Only use fifo after the port is initialized in console_write Wander Lairson Costa
2022-03-17 7:06 ` Jiri Slaby
2022-03-17 12:22 ` Wander Costa
2022-03-17 8:43 ` Ilpo Järvinen
2022-03-17 12:23 ` Wander Costa
2022-03-16 16:13 ` Andy Shevchenko [this message]
2022-03-16 16:14 ` [PATCH v4 0/5] tty/8250: Use fifo in 8250 console driver Andy Shevchenko
2022-03-16 16:37 ` Wander Costa
2022-03-17 15:47 ` Steven Rostedt
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=YjIMn/cBf7STIxBU@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=andre.goddard@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=macro@orcam.me.uk \
--cc=pali@kernel.org \
--cc=phil@raspberrypi.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=wander@redhat.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;
as well as URLs for NNTP newsgroup(s).