From: Jiri Slaby <jirislaby@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH] tty: serial: fsl_lpuart: count tty buffer overruns
Date: Tue, 11 Jan 2022 08:08:58 +0100 [thread overview]
Message-ID: <e6315e6b-78a6-0a8b-c693-9797a4519bd4@kernel.org> (raw)
In-Reply-To: <20220111061036.12638-1-sherry.sun@nxp.com>
On 11. 01. 22, 7:10, Sherry Sun wrote:
> Added support for counting the tty buffer overruns in fsl_lpuart driver
> like other uart drivers.
>
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
> drivers/tty/serial/fsl_lpuart.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
> index ce3e26144689..1e6f924d8507 100644
> --- a/drivers/tty/serial/fsl_lpuart.c
> +++ b/drivers/tty/serial/fsl_lpuart.c
...
> @@ -1117,6 +1119,7 @@ static void lpuart_copy_rx_to_tty(struct lpuart_port *sport)
> struct circ_buf *ring = &sport->rx_ring;
> unsigned long flags;
> int count = 0;
> + unsigned int copied = 0;
>
> if (lpuart_is_32(sport)) {
> unsigned long sr = lpuart32_read(&sport->port, UARTSTAT);
> @@ -1218,20 +1221,24 @@ static void lpuart_copy_rx_to_tty(struct lpuart_port *sport)
> if (ring->head < ring->tail) {
> count = sport->rx_sgl.length - ring->tail;
>
> - tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + copied = tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + if (copied != count)
Overall looks good, except tty_insert_flip_string returns an int and
count is also an int. Wouldn't it be more consistent to declare copied
as int too? This comparison would be without implicit conversion then.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2022-01-11 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 6:10 Sherry Sun
2022-01-11 7:08 ` Jiri Slaby [this message]
2022-01-11 8:06 ` Sherry Sun
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=e6315e6b-78a6-0a8b-c693-9797a4519bd4@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sherry.sun@nxp.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
all inboxes | Powered by JetHome®