linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	 Alexandra Winter <wintera@linux.ibm.com>,
	 Thorsten Winkler <twinkler@linux.ibm.com>,
	David Ahern <dsahern@kernel.org>,
	 Jay Vosburgh <jv@jvosburgh.net>,
	Andy Gospodarek <andy@greyhouse.net>,
	 Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
	 Sean Tranchetti <quic_stranche@quicinc.com>,
	 Paul Moore <paul@paul-moore.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	 Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	 Jiri Pirko <jiri@resnulli.us>,
	 Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	 Xin Long <lucien.xin@gmail.com>, Martin Schiller <ms@dev.tdt.de>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	 linux-security-module@vger.kernel.org,
	linux-sctp@vger.kernel.org,  linux-x25@vger.kernel.org
Subject: [PATCH net-next 10/13] sctp: Correct spelling in headers
Date: Thu, 22 Aug 2024 13:57:31 +0100	[thread overview]
Message-ID: <20240822-net-spell-v1-10-3a98971ce2d2@kernel.org> (raw)
In-Reply-To: <20240822-net-spell-v1-0-3a98971ce2d2@kernel.org>

Correct spelling in sctp.h and structs.h.
As reported by codespell.

Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: Xin Long <lucien.xin@gmail.com>
Cc: linux-sctp@vger.kernel.org
Signed-off-by: Simon Horman <horms@kernel.org>
---
 include/net/sctp/sctp.h    |  2 +-
 include/net/sctp/structs.h | 20 ++++++++++----------
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/include/net/sctp/sctp.h b/include/net/sctp/sctp.h
index a2310fa995f6..84e6b9fd5610 100644
--- a/include/net/sctp/sctp.h
+++ b/include/net/sctp/sctp.h
@@ -28,7 +28,7 @@
 #define __net_sctp_h__
 
 /* Header Strategy.
- *    Start getting some control over the header file depencies:
+ *    Start getting some control over the header file dependencies:
  *       includes
  *       constants
  *       structs
diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index f24a1bbcb3ef..31248cfdfb23 100644
--- a/include/net/sctp/structs.h
+++ b/include/net/sctp/structs.h
@@ -521,7 +521,7 @@ struct sctp_datamsg {
 	refcount_t refcnt;
 	/* When is this message no longer interesting to the peer? */
 	unsigned long expires_at;
-	/* Did the messenge fail to send? */
+	/* Did the message fail to send? */
 	int send_error;
 	u8 send_failed:1,
 	   can_delay:1,	/* should this message be Nagle delayed */
@@ -792,7 +792,7 @@ struct sctp_transport {
 		 */
 		hb_sent:1,
 
-		/* Is the Path MTU update pending on this tranport */
+		/* Is the Path MTU update pending on this transport */
 		pmtu_pending:1,
 
 		dst_pending_confirm:1,	/* need to confirm neighbour */
@@ -1223,7 +1223,7 @@ enum sctp_endpoint_type {
 };
 
 /*
- * A common base class to bridge the implmentation view of a
+ * A common base class to bridge the implementation view of a
  * socket (usually listening) endpoint versus an association's
  * local endpoint.
  * This common structure is useful for several purposes:
@@ -1353,7 +1353,7 @@ struct sctp_endpoint {
 	struct rcu_head rcu;
 };
 
-/* Recover the outter endpoint structure. */
+/* Recover the outer endpoint structure. */
 static inline struct sctp_endpoint *sctp_ep(struct sctp_ep_common *base)
 {
 	struct sctp_endpoint *ep;
@@ -1906,7 +1906,7 @@ struct sctp_association {
 	__u32 rwnd_over;
 
 	/* Keeps treack of rwnd pressure.  This happens when we have
-	 * a window, but not recevie buffer (i.e small packets).  This one
+	 * a window, but not receive buffer (i.e small packets).  This one
 	 * is releases slowly (1 PMTU at a time ).
 	 */
 	__u32 rwnd_press;
@@ -1994,7 +1994,7 @@ struct sctp_association {
 
 	/* ADDIP Section 5.2 Upon reception of an ASCONF Chunk.
 	 *
-	 * This is needed to implement itmes E1 - E4 of the updated
+	 * This is needed to implement items E1 - E4 of the updated
 	 * spec.  Here is the justification:
 	 *
 	 * Since the peer may bundle multiple ASCONF chunks toward us,
@@ -2005,7 +2005,7 @@ struct sctp_association {
 
 	/* These ASCONF chunks are waiting to be sent.
 	 *
-	 * These chunaks can't be pushed to outqueue until receiving
+	 * These chunks can't be pushed to outqueue until receiving
 	 * ASCONF_ACK for the previous ASCONF indicated by
 	 * addip_last_asconf, so as to guarantee that only one ASCONF
 	 * is in flight at any time.
@@ -2059,13 +2059,13 @@ struct sctp_association {
 	struct sctp_transport *new_transport;
 
 	/* SCTP AUTH: list of the endpoint shared keys.  These
-	 * keys are provided out of band by the user applicaton
+	 * keys are provided out of band by the user application
 	 * and can't change during the lifetime of the association
 	 */
 	struct list_head endpoint_shared_keys;
 
 	/* SCTP AUTH:
-	 * The current generated assocaition shared key (secret)
+	 * The current generated association shared key (secret)
 	 */
 	struct sctp_auth_bytes *asoc_shared_key;
 	struct sctp_shared_key *shkey;
@@ -2121,7 +2121,7 @@ enum {
 	SCTP_ASSOC_EYECATCHER = 0xa550c123,
 };
 
-/* Recover the outter association structure. */
+/* Recover the outer association structure. */
 static inline struct sctp_association *sctp_assoc(struct sctp_ep_common *base)
 {
 	struct sctp_association *asoc;

-- 
2.43.0


  parent reply	other threads:[~2024-08-22 12:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 12:57 [PATCH net-next 00/13] net: header and core spelling corrections Simon Horman
2024-08-22 12:57 ` [PATCH net-next 01/13] packet: Correct spelling in if_packet.h Simon Horman
2024-08-23 12:42   ` Willem de Bruijn
2024-08-22 12:57 ` [PATCH net-next 02/13] s390/iucv: Correct spelling in iucv.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 03/13] ip_tunnel: Correct spelling in ip_tunnels.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 04/13] ipv6: Correct spelling in ipv6.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 05/13] bonding: Correct spelling in headers Simon Horman
2024-08-22 12:57 ` [PATCH net-next 06/13] net: qualcomm: rmnet: Correct spelling in if_rmnet.h Simon Horman
2024-08-23  5:07   ` Subash Abhinov Kasiviswanathan (KS)
2024-08-22 12:57 ` [PATCH net-next 07/13] netlabel: Correct spelling in netlabel.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 08/13] NFC: Correct spelling in headers Simon Horman
2024-08-23 13:40   ` Krzysztof Kozlowski
2024-08-22 12:57 ` [PATCH net-next 09/13] net: sched: " Simon Horman
2024-08-22 12:57 ` Simon Horman [this message]
2024-08-22 14:01   ` [PATCH net-next 10/13] sctp: " Xin Long
2024-08-22 12:57 ` [PATCH net-next 11/13] x25: Correct spelling in x25.h Simon Horman
2024-08-23  5:27   ` Martin Schiller
2024-08-22 12:57 ` [PATCH net-next 12/13] net: Correct spelling in headers Simon Horman
2024-08-26 16:45   ` Jakub Kicinski
2024-08-27  8:25     ` Simon Horman
2024-08-22 12:57 ` [PATCH net-next 13/13] net: Correct spelling in net/core Simon Horman
2024-08-25  7:52 ` [PATCH net-next 00/13] net: header and core spelling corrections Philipp Stanner
2024-08-25  8:06   ` Krzysztof Kozlowski
2024-08-25  8:54   ` Simon Horman
2024-08-26 16:50 ` 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=20240822-net-spell-v1-10-3a98971ce2d2@kernel.org \
    --to=horms@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=jv@jvosburgh.net \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-x25@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=ms@dev.tdt.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=quic_stranche@quicinc.com \
    --cc=quic_subashab@quicinc.com \
    --cc=twinkler@linux.ibm.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=wintera@linux.ibm.com \
    --cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).