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
Subject: Re: [PATCH net 0/3] mptcp: Fixes for 5.17
Date: Fri, 25 Feb 2022 06:40:11 +0000 [thread overview]
Message-ID: <164577121118.6076.5592393879706573680.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220225005259.318898-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, 24 Feb 2022 16:52:56 -0800 you wrote:
> Patch 1 fixes an issue with the SIOCOUTQ ioctl in MPTCP sockets that
> have performed a fallback to TCP.
>
> Patch 2 is a selftest fix to correctly remove temp files.
>
> Patch 3 fixes a shift-out-of-bounds issue found by syzkaller.
>
> [...]
Here is the summary with links:
- [net,1/3] mptcp: accurate SIOCOUTQ for fallback socket
https://git.kernel.org/netdev/net/c/07c2c7a3b622
- [net,2/3] selftests: mptcp: do complete cleanup at exit
https://git.kernel.org/netdev/net/c/63bb8239d805
- [net,3/3] mptcp: Correctly set DATA_FIN timeout when number of retransmits is large
https://git.kernel.org/netdev/net/c/877d11f0332c
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-02-25 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 0:52 [PATCH net 0/3] mptcp: Fixes for 5.17 Mat Martineau
2022-02-25 0:52 ` [PATCH net 1/3] mptcp: accurate SIOCOUTQ for fallback socket Mat Martineau
2022-02-25 0:52 ` [PATCH net 2/3] selftests: mptcp: do complete cleanup at exit Mat Martineau
2022-02-25 0:52 ` [PATCH net 3/3] mptcp: Correctly set DATA_FIN timeout when number of retransmits is large Mat Martineau
2022-02-25 6:40 ` 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=164577121118.6076.5592393879706573680.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--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 \
/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.