All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Wander Costa' <wcosta@redhat.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "wander@redhat.com" <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>, Andrew Jeffery <andrew@aj.id.au>,
	"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] tty: serial: Use fifo in 8250 console driver
Date: Fri, 12 Nov 2021 11:58:02 +0000	[thread overview]
Message-ID: <590acddcf63344cd9a3295256b118586@AcuMS.aculab.com> (raw)
In-Reply-To: <CAAq0SU=wYZ9e9NJvwcLvEvxj-J7PhAPFjRAu2uFVYPprR7A_qQ@mail.gmail.com>

> > Here is a translation of my comment to a roadmap.
> >
> > 1. Introduce yet another UART quirk or capability (see corresponding
> > UART_CAP_* or UART_*_QUIRK definitions)
> > 2. Add your patch conditionally based on the above
> > 3. Enable it on UART(s) you _have tested_
> >
> Thank you for the feedback, I submitted a v2 patch with your proposed changes,

Or put the UART into loopback and see how many characters will
actually fit in the fifos.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2021-11-12 11:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 20:14 [PATCH] tty: serial: Use fifo in 8250 console driver wander
     [not found] ` <CAHp75VeZBp4gKvGBDzaD=EpGRDZ1-wTvD8K9Ui6Q59kDjmkXmQ@mail.gmail.com>
2021-11-01 15:22   ` Wander Costa
2021-11-01 15:32     ` Andy Shevchenko
2021-11-10 12:10       ` Wander Costa
2021-11-12 11:58         ` David Laight [this message]
2022-01-25  8:39 ` Jon Hunter
2022-01-25  8:50   ` Greg Kroah-Hartman
2022-01-25  9:03     ` Jon Hunter
2022-01-25  9:08   ` Jiri Slaby
2022-01-25  9:36     ` Jiri Slaby
2022-01-25 10:06       ` Jon Hunter
2022-01-25 10:29         ` Wander Costa
2022-01-25 12:40           ` Jon Hunter
2022-01-25 16:53             ` Andy Shevchenko
2022-01-25 16:54               ` Andy Shevchenko
2022-01-25 18:40                 ` Wander Costa
2022-01-26  8:52                   ` Greg Kroah-Hartman
2022-01-26 12:09                     ` Andy Shevchenko
2022-01-26 13:23                       ` Wander Costa
2022-01-26 13:34                         ` Andy Shevchenko
2022-01-27 18:10                     ` Theodore Y. Ts'o
2022-01-25 10:18       ` Wander Costa
2022-01-25 10:38         ` Jiri Slaby

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=590acddcf63344cd9a3295256b118586@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=andrew@aj.id.au \
    --cc=andy.shevchenko@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=macro@orcam.me.uk \
    --cc=wander@redhat.com \
    --cc=wcosta@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 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.