All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	matthieu.baerts@tessares.net, mptcp@lists.linux.dev,
	pabeni@redhat.com, fw@strlen.de
Subject: Re: [PATCH net 0/2] mptcp: 32-bit sequence number improvements
Date: Mon, 21 Jun 2021 21:50:04 +0000	[thread overview]
Message-ID: <162431220440.17422.8872440735370690772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210618220221.99172-1-mathew.j.martineau@linux.intel.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Fri, 18 Jun 2021 15:02:19 -0700 you wrote:
> MPTCP-level sequence numbers are 64 bits, but RFC 8684 allows use of
> 32-bit sequence numbers in the DSS option to save header space. Those
> 32-bit numbers are the least significant bits of the full 64-bit
> sequence number, so the receiver must infer the correct upper 32 bits.
> 
> These two patches improve the logic for determining the full 64-bit
> sequence numbers when the 32-bit truncated version has wrapped around.
> 
> [...]

Here is the summary with links:
  - [net,1/2] mptcp: fix bad handling of 32 bit ack wrap-around
    https://git.kernel.org/netdev/net/c/1502328f17ab
  - [net,2/2] mptcp: fix 32 bit DSN expansion
    https://git.kernel.org/netdev/net/c/5957a8901db4

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-06-21 21:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 22:02 [PATCH net 0/2] mptcp: 32-bit sequence number improvements Mat Martineau
2021-06-18 22:02 ` [PATCH net 1/2] mptcp: fix bad handling of 32 bit ack wrap-around Mat Martineau
2021-06-18 22:02 ` [PATCH net 2/2] mptcp: fix 32 bit DSN expansion Mat Martineau
2021-06-21 21:50 ` patchwork-bot+netdevbpf [this message]

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=162431220440.17422.8872440735370690772.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.