From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH] mptcp: fix warnings reported by checkpatch
Date: Thu, 10 Oct 2019 16:27:43 +0200 [thread overview]
Message-ID: <20191010142745.6436-3-matthieu.baerts@tessares.net> (raw)
In-Reply-To: 20191010142745.6436-1-matthieu.baerts@tessares.net
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
WARNING: 'regarless' may be misspelled - perhaps 'regardless'?
#13:
Note that now we need to call __mptcp_init_sock() regarless of mptcp
Signed-off-by: Matthieu Baerts <matthieu.baerts(a)tessares.net>
---
Notes:
to be squashed in "mptcp: queue data for mptcp level retransmission"
.topmsg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.topmsg b/.topmsg
index 7e583db6e3ab..ab57e824a32c 100644
--- a/.topmsg
+++ b/.topmsg
@@ -10,7 +10,7 @@ the current page fragment can always host an MPTCP rtx queue entry.
The MPTCP rtx queue is flushed at disconnect() and close() time
-Note that now we need to call __mptcp_init_sock() regarless of mptcp
+Note that now we need to call __mptcp_init_sock() regardless of mptcp
enable status, as the destructor will try to walk the rtx_queue.
Signed-off-by: Paolo Abeni <pabeni(a)redhat.com>
--
2.20.1
next reply other threads:[~2019-10-10 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 14:27 Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-10 14:27 [MPTCP] [PATCH] mptcp: fix warnings reported by checkpatch Matthieu Baerts
2019-10-10 14:27 Matthieu Baerts
2019-10-10 14:27 Matthieu Baerts
2019-10-10 14:27 Matthieu Baerts
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=20191010142745.6436-3-matthieu.baerts@tessares.net \
--to=unknown@example.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.