From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <martineau@kernel.org>
Cc: matttbe@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
mptcp@lists.linux.dev, kishen.maloor@intel.com, fw@strlen.de,
stable@vger.kernel.org, geliang.tang@suse.com
Subject: Re: [PATCH net 0/3] mptcp: Fixes and maintainer email update for v6.6
Date: Thu, 05 Oct 2023 16:40:25 +0000 [thread overview]
Message-ID: <169652402541.29548.3696837409901235215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231004-send-net-20231004-v1-0-28de4ac663ae@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 04 Oct 2023 13:38:10 -0700 you wrote:
> Patch 1 addresses a race condition in MPTCP "delegated actions"
> infrastructure. Affects v5.19 and later.
>
> Patch 2 removes an unnecessary restriction that did not allow additional
> outgoing subflows using the local address of the initial MPTCP subflow.
> v5.16 and later.
>
> [...]
Here is the summary with links:
- [net,1/3] mptcp: fix delegated action races
https://git.kernel.org/netdev/net/c/a5efdbcece83
- [net,2/3] mptcp: userspace pm allow creating id 0 subflow
https://git.kernel.org/netdev/net/c/e5ed101a6028
- [net,3/3] MAINTAINERS: update Matthieu's email address
https://git.kernel.org/netdev/net/c/8eed6ee362b0
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:[~2023-10-05 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 20:38 [PATCH net 0/3] mptcp: Fixes and maintainer email update for v6.6 Mat Martineau
2023-10-04 20:38 ` [PATCH net 1/3] mptcp: fix delegated action races Mat Martineau
2023-10-04 20:38 ` [PATCH net 2/3] mptcp: userspace pm allow creating id 0 subflow Mat Martineau
2023-10-05 16: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=169652402541.29548.3696837409901235215.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=kishen.maloor@intel.com \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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