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-next 0/3] mptcp: Updates for net-next
Date: Mon, 16 May 2022 20:20:14 +0000 [thread overview]
Message-ID: <165273241421.3924.625171959579879205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220514002115.725976-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 May 2022 17:21:12 -0700 you wrote:
> Three independent fixes/features from the MPTCP tree:
>
> Patch 1 is a selftest workaround for older iproute2 packages.
>
> Patch 2 removes superfluous locks that were added with recent MP_FAIL
> patches.
>
> [...]
Here is the summary with links:
- [net-next,1/3] selftests: mptcp: fix a mp_fail test warning
https://git.kernel.org/netdev/net-next/c/c43ce39870b3
- [net-next,2/3] Revert "mptcp: add data lock for sk timers"
https://git.kernel.org/netdev/net-next/c/0ea5374255a9
- [net-next,3/3] mptcp: sockopt: add TCP_DEFER_ACCEPT support
https://git.kernel.org/netdev/net-next/c/ea1e301d04b7
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-16 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 0:21 [PATCH net-next 0/3] mptcp: Updates for net-next Mat Martineau
2022-05-14 0:21 ` [PATCH net-next 1/3] selftests: mptcp: fix a mp_fail test warning Mat Martineau
2022-05-16 20:13 ` Jakub Kicinski
2022-05-17 7:01 ` Matthieu Baerts
2022-05-14 0:21 ` [PATCH net-next 2/3] Revert "mptcp: add data lock for sk timers" Mat Martineau
2022-05-14 0:21 ` [PATCH net-next 3/3] mptcp: sockopt: add TCP_DEFER_ACCEPT support Mat Martineau
2022-05-16 20:20 ` 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=165273241421.3924.625171959579879205.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;
as well as URLs for NNTP newsgroup(s).