[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 6 Jun 2023 15:56:33 +0200
From: Simon Horman <simon.horman@...igine.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>
Cc: Eric Dumazet <edumazet@...gle.com>,
"David S . Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] tcp: Spelling s/curcuit/circuit/
On Tue, Jun 06, 2023 at 12:04:57PM +0200, Geert Uytterhoeven wrote:
> Fix a misspelling of "circuit".
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> net/ipv4/tcp_input.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
> index bf8b22218dd46863..3403ed457baf781e 100644
> --- a/net/ipv4/tcp_input.c
> +++ b/net/ipv4/tcp_input.c
> @@ -1131,7 +1131,7 @@ static void tcp_count_delivered(struct tcp_sock *tp, u32 delivered,
> * L|R 1 - orig is lost, retransmit is in flight.
> * S|R 1 - orig reached receiver, retrans is still in flight.
> * (L|S|R is logically valid, it could occur when L|R is sacked,
> - * but it is equivalent to plain S and code short-curcuits it to S.
> + * but it is equivalent to plain S and code short-circuits it to S.
> * L|S is logically invalid, it would mean -1 packet in flight 8))
> *
> * These 6 states form finite state machine, controlled by the following events:
Hi Geert,
I have no strong feelings about this.
But I do notice that codespell flags a moderate number
of other spelling mistakes in this file. Perhaps they
could also be fixed at the same time as this one?
Powered by blists - more mailing lists