[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025121710-engulf-feminism-f536@gregkh>
Date: Wed, 17 Dec 2025 14:56:22 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Harikrishna Srinivasan <harikrs0905@...il.com>
Cc: Jiri Slaby <jirislaby@...nel.org>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] serial: pxa: Fix comment typo
On Mon, Dec 15, 2025 at 12:28:46AM -0700, Harikrishna Srinivasan wrote:
> Fix a spelling mistake in a driver comment.
>
> Signed-off-by: Harikrishna Srinivasan <harikrs0905@...il.com>
> ---
> drivers/tty/serial/pxa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/pxa.c b/drivers/tty/serial/pxa.c
> index e395ff29c1a2..19d85398e394 100644
> --- a/drivers/tty/serial/pxa.c
> +++ b/drivers/tty/serial/pxa.c
> @@ -99,7 +99,7 @@ static inline void receive_chars(struct uart_pxa_port *up, int *status)
> * Specification Update (May 2005)
> *
> * Step 2
> - * Disable the Reciever Time Out Interrupt via IER[RTOEI]
> + * Disable the receiver timeout interrupt via IER[RTOEI]
> */
> up->ier &= ~UART_IER_RTOIE;
> serial_out(up, UART_IER, up->ier);
> --
> 2.43.0
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists