From: Wander Costa <wcosta@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Wander Lairson Costa" <wander@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Johan Hovold" <johan@kernel.org>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Lukas Wunner" <lukas@wunner.de>, "Pali Rohár" <pali@kernel.org>,
"Andrew Jeffery" <andrew@aj.id.au>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH v3 1/1] tty: serial: Use fifo in 8250 console driver
Date: Tue, 25 Jan 2022 11:26:03 -0300 [thread overview]
Message-ID: <CAAq0SUkuG2uyouBhT5yDiq_KbOGUCO=9ondq6dkt1QZLN_C4uA@mail.gmail.com> (raw)
In-Reply-To: <YfAFAcYmJ+Zrontd@linutronix.de>
On Tue, Jan 25, 2022 at 11:11 AM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2022-01-25 10:15:04 [-0300], Wander Costa wrote:
> > There is another thread[1] reporting some issues with this patch.
> > There, this diff seems to fix the problems, could you please try and
> > report if it works for you too?
>
> Nope. Still there.
I will check on my side if I see something similar. Do you still get
lines lost as well?
next prev parent reply other threads:[~2022-01-25 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 11:28 [PATCH v3 0/1] tty: serial: Use fifo in 8250 console driver Wander Lairson Costa
2021-12-22 11:28 ` [PATCH v3 1/1] " Wander Lairson Costa
2022-01-25 13:07 ` Sebastian Andrzej Siewior
2022-01-25 13:15 ` Wander Costa
2022-01-25 14:11 ` Sebastian Andrzej Siewior
2022-01-25 14:26 ` Wander Costa [this message]
2022-01-25 14:34 ` Sebastian Andrzej Siewior
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='CAAq0SUkuG2uyouBhT5yDiq_KbOGUCO=9ondq6dkt1QZLN_C4uA@mail.gmail.com' \
--to=wcosta@redhat.com \
--cc=andrew@aj.id.au \
--cc=bigeasy@linutronix.de \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--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=tglx@linutronix.de \
--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).