diff mbox series

Update commit message for "mptcp: Implement MPTCP receive path"

Message ID 20200118010657.22436-1-mathew.j.martineau@linux.intel.com
State Accepted, archived
Delegated to: Matthieu Baerts
Headers show
Series Update commit message for "mptcp: Implement MPTCP receive path" | expand

Commit Message

Mat Martineau Jan. 18, 2020, 1:06 a.m. UTC
Fix minor typos.

Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
---
 .topmsg | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

Comments

Matthieu Baerts Jan. 20, 2020, 4:09 p.m. UTC | #1
Hi Mat,

On 18/01/2020 02:06, Mat Martineau wrote:
> Fix minor typos.

Thank you for the patch!

- d2c4d63e88f1: "squashed" in "mptcp: Implement MPTCP receive path"

TG export will be done soon.

Cheers,
Matt
diff mbox series

Patch

diff --git a/.topmsg b/.topmsg
index 75ae84b862ce..5a55ac729038 100644
--- a/.topmsg
+++ b/.topmsg
@@ -6,13 +6,13 @@  fields. MPTCP fields are parsed from the TCP option header and placed in
 an skb extension, allowing the upper MPTCP layer to access MPTCP
 options after the skb has gone through the TCP stack.
 
-The subflow implements it's own data_ready() ops, which ensures that
-the pending data is in sequence - according to MPTCP seq number -
-dropping out-of-seq skbs.  The DATA_READY bit flag is set if this
-is the case.  This allows the MPTCP socket layer to determine if more
-data is available without having to consult the individual subflows.
+The subflow implements its own data_ready() ops, which ensures that the
+pending data is in sequence - according to MPTCP seq number - dropping
+out-of-seq skbs. The DATA_READY bit flag is set if this is the case.
+This allows the MPTCP socket layer to determine if more data is
+available without having to consult the individual subflows.
 
-It additionally validates the current mapping and propagate EoF events
+It additionally validates the current mapping and propagates EoF events
 to the connection socket.
 
 Co-developed-by: Paolo Abeni <pabeni@redhat.com>