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,
imx@lists.linux.dev, shenwei.wang@nxp.com
Subject: Re: [PATCH V2 3/3] tty: serial: lpuart: rename register variables more specifically
Date: Tue, 11 Mar 2025 04:50:41 +0100 [thread overview]
Message-ID: <7b0bfff1-7398-4236-9579-7fc2cd450c44@kernel.org> (raw)
In-Reply-To: <20250311033336.1254842-4-sherry.sun@nxp.com>
On 11. 03. 25, 4:33, Sherry Sun wrote:
> There are many fuzzy register variables in the lpuart driver, such as
> temp, tmp, val, reg. Let's give these register variables more specific
> names.
>
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
> drivers/tty/serial/fsl_lpuart.c | 220 ++++++++++++++++----------------
> 1 file changed, 110 insertions(+), 110 deletions(-)
>
> diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
> index f830b5a3ba8e..901c83461bfc 100644
> --- a/drivers/tty/serial/fsl_lpuart.c
> +++ b/drivers/tty/serial/fsl_lpuart.c
> @@ -441,36 +441,36 @@ static unsigned int lpuart_get_baud_clk_rate(struct lpuart_port *sport)
>
> static void lpuart_stop_tx(struct uart_port *port)
> {
> - unsigned char temp;
> + unsigned char cr2;
Overall looks good. In cases like these (there are many), you should
have switched this to u8 in patch 1/3 too ;).
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-03-11 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 3:33 [PATCH V2 0/3] tty: serial: fsl_lpuart: cleanup lpuart driver Sherry Sun
2025-03-11 3:33 ` [PATCH V2 1/3] tty: serial: fsl_lpuart: Use u32 for register variables Sherry Sun
2025-03-11 3:33 ` [PATCH V2 2/3] tty: serial: fsl_lpuart: use port struct directly to simply code Sherry Sun
2025-03-11 3:33 ` [PATCH V2 3/3] tty: serial: lpuart: rename register variables more specifically Sherry Sun
2025-03-11 3:50 ` Jiri Slaby [this message]
2025-03-11 6:57 ` 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=7b0bfff1-7398-4236-9579-7fc2cd450c44@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shenwei.wang@nxp.com \
--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