All of lore.kernel.org
 help / color / mirror / Atom feed
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:41 +0200	[thread overview]
Message-ID: <20191010142745.6436-1-matthieu.baerts@tessares.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

WARNING: line over 80 characters
#233: FILE: net/mptcp/options.c:47:
+                * negotiated, the receiver MUST close the subflow with a RST as it is

Signed-off-by: Matthieu Baerts <matthieu.baerts(a)tessares.net>
---

Notes:
    to be squashed in "mptcp: Handle MPTCP TCP options"

 net/mptcp/options.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/mptcp/options.c b/net/mptcp/options.c
index cee4280647fe..adf65d3ff27b 100644
--- a/net/mptcp/options.c
+++ b/net/mptcp/options.c
@@ -44,8 +44,8 @@ void mptcp_parse_option(const unsigned char *ptr, int opsize,
 		 *
 		 * Section 3.3.0:
 		 * "If a checksum is not present when its use has been
-		 * negotiated, the receiver MUST close the subflow with a RST as it is
-		 * considered broken."
+		 * negotiated, the receiver MUST close the subflow with a RST as
+		 * it is considered broken."
 		 *
 		 * We don't implement DSS checksum - fall back to TCP.
 		 */
-- 
2.20.1

             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]
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-1-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.