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, fw@strlen.de,
geliang.tang@suse.com, matthieu.baerts@tessares.net,
mptcp@lists.linux.dev
Subject: Re: [PATCH net 0/9] mptcp: Fixes for 5.19
Date: Wed, 29 Jun 2022 04:00:15 +0000 [thread overview]
Message-ID: <165647521550.15342.17491165529630810403.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220628010243.166605-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Jun 2022 18:02:34 -0700 you wrote:
> Several categories of fixes from the mptcp tree:
>
> Patches 1-3 are fixes related to MP_FAIL and FASTCLOSE, to make sure
> MIBs are accurate, and to handle MP_FAIL transmission and responses at
> the correct times. sk_timer conflicts are also resolved.
>
> Patches 4 and 6 handle two separate race conditions, one at socket
> shutdown and one with unaccepted subflows.
>
> [...]
Here is the summary with links:
- [net,1/9] mptcp: fix error mibs accounting
https://git.kernel.org/netdev/net/c/0c1f78a49af7
- [net,2/9] mptcp: introduce MAPPING_BAD_CSUM
https://git.kernel.org/netdev/net/c/31bf11de146c
- [net,3/9] mptcp: invoke MP_FAIL response when needed
https://git.kernel.org/netdev/net/c/76a13b315709
- [net,4/9] mptcp: fix shutdown vs fallback race
https://git.kernel.org/netdev/net/c/d51991e2e314
- [net,5/9] mptcp: consistent map handling on failure
https://git.kernel.org/netdev/net/c/f745a3ebdfb9
- [net,6/9] mptcp: fix race on unaccepted mptcp sockets
https://git.kernel.org/netdev/net/c/6aeed9045071
- [net,7/9] selftests: mptcp: more stable diag tests
https://git.kernel.org/netdev/net/c/42fb6cddec3b
- [net,8/9] mptcp: fix conflict with <netinet/in.h>
https://git.kernel.org/netdev/net/c/06e445f740c1
- [net,9/9] selftests: mptcp: Initialize variables to quiet gcc 12 warnings
https://git.kernel.org/netdev/net/c/fd37c2ecb21f
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-06-29 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 1:02 [PATCH net 0/9] mptcp: Fixes for 5.19 Mat Martineau
2022-06-28 1:02 ` [PATCH net 1/9] mptcp: fix error mibs accounting Mat Martineau
2022-06-28 1:02 ` [PATCH net 2/9] mptcp: introduce MAPPING_BAD_CSUM Mat Martineau
2022-06-28 1:02 ` [PATCH net 3/9] mptcp: invoke MP_FAIL response when needed Mat Martineau
2022-06-28 1:02 ` [PATCH net 4/9] mptcp: fix shutdown vs fallback race Mat Martineau
2022-06-28 1:02 ` [PATCH net 5/9] mptcp: consistent map handling on failure Mat Martineau
2022-06-28 1:02 ` [PATCH net 6/9] mptcp: fix race on unaccepted mptcp sockets Mat Martineau
2022-06-28 1:02 ` [PATCH net 7/9] selftests: mptcp: more stable diag tests Mat Martineau
2022-06-28 1:02 ` [PATCH net 8/9] mptcp: fix conflict with <netinet/in.h> Mat Martineau
2022-06-28 1:02 ` [PATCH net 9/9] selftests: mptcp: Initialize variables to quiet gcc 12 warnings Mat Martineau
2022-06-29 4:00 ` 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=165647521550.15342.17491165529630810403.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang.tang@suse.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