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,
pabeni@redhat.com, edumazet@google.com,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net 0/2] mptcp: Subflow accounting fix
Date: Sat, 14 May 2022 00:10:12 +0000 [thread overview]
Message-ID: <165248701290.14999.16227834214314125903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220512232642.541301-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 May 2022 16:26:40 -0700 you wrote:
> This series contains a bug fix affecting the in-kernel path manager
> (patch 1), where closing subflows would sometimes not adjust the PM's
> count of active subflows. Patch 2 updates the selftests to exercise the
> new code.
>
> Paolo Abeni (2):
> mptcp: fix subflow accounting on close
> selftests: mptcp: add subflow limits test-cases
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: fix subflow accounting on close
https://git.kernel.org/netdev/net/c/95d686517884
- [net,2/2] selftests: mptcp: add subflow limits test-cases
https://git.kernel.org/netdev/net/c/e274f7154008
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-14 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 23:26 [PATCH net 0/2] mptcp: Subflow accounting fix Mat Martineau
2022-05-12 23:26 ` [PATCH net 1/2] mptcp: fix subflow accounting on close Mat Martineau
2022-05-12 23:26 ` [PATCH net 2/2] selftests: mptcp: add subflow limits test-cases Mat Martineau
2022-05-14 0: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=165248701290.14999.16227834214314125903.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox