From: Simon Horman <simon.horman@corigine.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: Spelling s/curcuit/circuit/
Date: Tue, 6 Jun 2023 15:56:33 +0200 [thread overview]
Message-ID: <ZH87EZd9goHN2oPX@corigine.com> (raw)
In-Reply-To: <41454fc12506c2620d2dbc03e59a4ba28fd48f22.1686045877.git.geert+renesas@glider.be>
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@glider.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?
next prev parent reply other threads:[~2023-06-06 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:04 [PATCH] tcp: Spelling s/curcuit/circuit/ Geert Uytterhoeven
2023-06-06 13:52 ` Larysa Zaremba
2023-06-06 13:56 ` Simon Horman [this message]
2023-06-06 14:05 ` [PATCH RESEND net-next] " Geert Uytterhoeven
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=ZH87EZd9goHN2oPX@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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