From: Avinash Duduskar <avinash.duduskar@gmail.com>
To: netdev@vger.kernel.org
Cc: achender@kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next] rds: tcp_listen: fix typos in comments
Date: Wed, 13 May 2026 03:25:31 +0530 [thread overview]
Message-ID: <20260512215531.1988662-1-avinash.duduskar@gmail.com> (raw)
Two typos in comments:
- "reconneect" -> "reconnect" (block comment above
rds_tcp_accept_one_path()).
- "acccepted" -> "accepted" (block comment inside
rds_tcp_conn_slots_available()).
Signed-off-by: Avinash Duduskar <avinash.duduskar@gmail.com>
---
net/rds/tcp_listen.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/rds/tcp_listen.c b/net/rds/tcp_listen.c
index 08a506aa7ce7..a3db9b057084 100644
--- a/net/rds/tcp_listen.c
+++ b/net/rds/tcp_listen.c
@@ -69,7 +69,7 @@ rds_tcp_get_peer_sport(struct socket *sock)
/* rds_tcp_accept_one_path(): if accepting on cp_index > 0, make sure the
* client's ipaddr < server's ipaddr. Otherwise, close the accepted
- * socket and force a reconneect from smaller -> larger ip addr. The reason
+ * socket and force a reconnect from smaller -> larger ip addr. The reason
* we special case cp_index 0 is to allow the rds probe ping itself to itself
* get through efficiently.
*/
@@ -143,7 +143,7 @@ void rds_tcp_conn_slots_available(struct rds_connection *conn, bool fan_out)
*
* Doing so is necessary to address the case where an
* incoming connection on "rds_tcp_listen_sock" is ready
- * to be acccepted prior to a free slot being available:
+ * to be accepted prior to a free slot being available:
* the -ENOBUFS case in "rds_tcp_accept_one".
*/
rds_tcp_accept_work(rtn);
base-commit: 73d587ae684d176fac9db94173f77d78a794ea4f
--
2.54.0
next reply other threads:[~2026-05-12 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 21:55 Avinash Duduskar [this message]
2026-05-13 5:49 ` [PATCH net-next] rds: tcp_listen: fix typos in comments Allison Henderson
2026-05-15 0:20 ` patchwork-bot+netdevbpf
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=20260512215531.1988662-1-avinash.duduskar@gmail.com \
--to=avinash.duduskar@gmail.com \
--cc=achender@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.