public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu Jiaoliang <yujiaoliang@vivo.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Xin Long <lucien.xin@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: [PATCH v1 net-next] sctp: Fix typos in comments across various files
Date: Tue, 24 Sep 2024 14:22:03 +0800	[thread overview]
Message-ID: <20240924062203.3127621-1-yujiaoliang@vivo.com> (raw)

This commit corrects spelling errors in comments
within the stcp subsystem to enhance clarity and
maintainability of the code.

Signed-off-by: Yu Jiaoliang <yujiaoliang@vivo.com>
---
 net/sctp/auth.c   | 4 ++--
 net/sctp/chunk.c  | 2 +-
 net/sctp/socket.c | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/net/sctp/auth.c b/net/sctp/auth.c
index c58fffc86a0c..4bec21f8cb36 100644
--- a/net/sctp/auth.c
+++ b/net/sctp/auth.c
@@ -460,7 +460,7 @@ int sctp_auth_init_hmacs(struct sctp_endpoint *ep, gfp_t gfp)
 	if (ep->auth_hmacs)
 		return 0;
 
-	/* Allocated the array of pointers to transorms */
+	/* Allocated the array of pointers to transforms */
 	ep->auth_hmacs = kcalloc(SCTP_AUTH_NUM_HMACS,
 				 sizeof(struct crypto_shash *),
 				 gfp);
@@ -774,7 +774,7 @@ int sctp_auth_ep_add_chunkid(struct sctp_endpoint *ep, __u8 chunk_id)
 	return 0;
 }
 
-/* Add hmac identifires to the endpoint list of supported hmac ids */
+/* Add hmac identifiers to the endpoint list of supported hmac ids */
 int sctp_auth_ep_set_hmacs(struct sctp_endpoint *ep,
 			   struct sctp_hmacalgo *hmacs)
 {
diff --git a/net/sctp/chunk.c b/net/sctp/chunk.c
index fd4f8243cc35..19f4562a3b7f 100644
--- a/net/sctp/chunk.c
+++ b/net/sctp/chunk.c
@@ -68,7 +68,7 @@ void sctp_datamsg_free(struct sctp_datamsg *msg)
 	sctp_datamsg_put(msg);
 }
 
-/* Final destructruction of datamsg memory. */
+/* Final destruction of datamsg memory. */
 static void sctp_datamsg_destroy(struct sctp_datamsg *msg)
 {
 	struct sctp_association *asoc = NULL;
diff --git a/net/sctp/socket.c b/net/sctp/socket.c
index 32f76f1298da..9fe18414a355 100644
--- a/net/sctp/socket.c
+++ b/net/sctp/socket.c
@@ -6631,7 +6631,7 @@ static int sctp_getsockopt_associnfo(struct sock *sk, int len,
 	    sctp_style(sk, UDP))
 		return -EINVAL;
 
-	/* Values correspoinding to the specific association */
+	/* Values corresponding to the specific association */
 	if (asoc) {
 		assocparams.sasoc_asocmaxrxt = asoc->max_retrans;
 		assocparams.sasoc_peer_rwnd = asoc->peer.rwnd;
-- 
2.34.1


             reply	other threads:[~2024-09-24  6:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  6:22 Yu Jiaoliang [this message]
2024-09-24  8:11 ` [PATCH v1 net-next] sctp: Fix typos in comments across various files Maxime Chevallier

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=20240924062203.3127621-1-yujiaoliang@vivo.com \
    --to=yujiaoliang@vivo.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --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