Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com
Subject: Re: [PATCHv2 net 0/2] sctp: improve the pmtu probe in Search Complete state
Date: Sun, 25 Jul 2021 22:10:05 +0000	[thread overview]
Message-ID: <162725100516.14953.14806239089098913539.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1627234857.git.lucien.xin@gmail.com>

Hello:

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

On Sun, 25 Jul 2021 13:42:49 -0400 you wrote:
> Timo recently suggested to use the loss of (data) packets as
> indication to send pmtu probe for Search Complete state, which
> should also be implied by RFC8899. This patchset is to change
> the current one that is doing probe with current pmtu all the
> time.
> 
> v1->v2:
>   - see Patch 2/2.
> 
> [...]

Here is the summary with links:
  - [PATCHv2,net,1/2] sctp: improve the code for pmtu probe send and recv update
    https://git.kernel.org/netdev/net/c/058e6e0ed0ea
  - [PATCHv2,net,2/2] sctp: send pmtu probe only if packet loss in Search Complete state
    https://git.kernel.org/netdev/net/c/eacf078cf4c7

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-07-25 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 17:42 [PATCHv2 net 0/2] sctp: improve the pmtu probe in Search Complete state Xin Long
2021-07-25 17:42 ` [PATCHv2 net 1/2] sctp: improve the code for pmtu probe send and recv update Xin Long
2021-07-25 17:42 ` [PATCHv2 net 2/2] sctp: send pmtu probe only if packet loss in Search Complete state Xin Long
2021-07-25 22:10 ` 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=162725100516.14953.14806239089098913539.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@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 NNTP newsgroup(s).