From: Shubh <shubhisroking@gmail.com>
To: linux-sctp@vger.kernel.org
Cc: Shubh <shubhisroking@gmail.com>
Subject: [PATCH] sctp: Fix spelling mistake "tranport" -> "transport"
Date: Sat, 2 Sep 2023 11:38:18 +0530 [thread overview]
Message-ID: <20230902060818.35184-1-shubhisroking@gmail.com> (raw)
Signed-off-by: Shubh <shubhisroking@gmail.com>
---
include/net/sctp/structs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index 5a24d6d85..caea9ab73 100644
--- a/include/net/sctp/structs.h
+++ b/include/net/sctp/structs.h
@@ -795,7 +795,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 */
--
2.42.0
next reply other threads:[~2023-09-02 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 6:08 Shubh [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-02 9:34 [PATCH] sctp: Fix spelling mistake "tranport" -> "transport" Shubh
2023-09-14 15:23 ` Marcelo Ricardo Leitner
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=20230902060818.35184-1-shubhisroking@gmail.com \
--to=shubhisroking@gmail.com \
--cc=linux-sctp@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).