From: Greg KH <gregkh@linuxfoundation.org>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: jirislaby@kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
shenwei.wang@nxp.com
Subject: Re: [PATCH V4 0/3] tty: serial: fsl_lpuart: cleanup lpuart driver
Date: Fri, 11 Apr 2025 16:51:07 +0200 [thread overview]
Message-ID: <2025041157-supply-joyfully-8b9c@gregkh> (raw)
In-Reply-To: <20250321073950.108820-1-sherry.sun@nxp.com>
On Fri, Mar 21, 2025 at 03:39:47PM +0800, Sherry Sun wrote:
> Do some cleanup for lpuart driver, no functionality change.
>
> Changes in V4:
> 1. Fix unused variable 'sport' warning in patch#2 reported by kernel test robot.
>
> Changes in V3:
> 1. Add the change to covert unsigned char to u8 in the first patch as Jiri suggested.
>
> Changes in V2:
> 1. Add the third patch to rename the register variables as Jiri suggested.
>
> Sherry Sun (3):
> tty: serial: fsl_lpuart: Use u32 and u8 for register variables
> tty: serial: fsl_lpuart: use port struct directly to simply code
> tty: serial: fsl_lpuart: rename register variables more specifically
>
> drivers/tty/serial/fsl_lpuart.c | 472 ++++++++++++++++----------------
> 1 file changed, 231 insertions(+), 241 deletions(-)
>
> --
> 2.34.1
>
None of this applies to 6.15-rc1, what went wrong?
next prev parent reply other threads:[~2025-04-11 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 7:39 [PATCH V4 0/3] tty: serial: fsl_lpuart: cleanup lpuart driver Sherry Sun
2025-03-21 7:39 ` [PATCH V4 1/3] tty: serial: fsl_lpuart: Use u32 and u8 for register variables Sherry Sun
2025-03-21 7:39 ` [PATCH V4 2/3] tty: serial: fsl_lpuart: use port struct directly to simply code Sherry Sun
2025-03-21 7:39 ` [PATCH V4 3/3] tty: serial: fsl_lpuart: rename register variables more specifically Sherry Sun
2025-03-21 12:37 ` [PATCH V4 0/3] tty: serial: fsl_lpuart: cleanup lpuart driver Fabio Estevam
2025-04-11 14:51 ` Greg KH [this message]
2025-04-13 11:56 ` 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=2025041157-supply-joyfully-8b9c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--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