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/7] mptcp: Path manager fixes for 5.19
Date: Wed, 06 Jul 2022 12:00:20 +0000 [thread overview]
Message-ID: <165710882054.23384.2979823140272634407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220705213217.146898-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 5 Jul 2022 14:32:10 -0700 you wrote:
> The MPTCP userspace path manager is new in 5.19, and these patches fix
> some issues in that new code.
>
> Patches 1-3 fix path manager locking issues.
>
> Patches 4 and 5 allow userspace path managers to change priority of
> established subflows using the existing MPTCP_PM_CMD_SET_FLAGS generic
> netlink command. Includes corresponding self test update.
>
> [...]
Here is the summary with links:
- [net,1/7] mptcp: fix locking in mptcp_nl_cmd_sf_destroy()
https://git.kernel.org/netdev/net/c/5ccecaec5c1e
- [net,2/7] mptcp: Avoid acquiring PM lock for subflow priority changes
https://git.kernel.org/netdev/net/c/c21b50d5912b
- [net,3/7] mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags
https://git.kernel.org/netdev/net/c/a657430260e5
- [net,4/7] mptcp: netlink: issue MP_PRIO signals from userspace PMs
https://git.kernel.org/netdev/net/c/892f396c8e68
- [net,5/7] selftests: mptcp: userspace PM support for MP_PRIO signals
https://git.kernel.org/netdev/net/c/ca188a25d43f
- [net,6/7] mptcp: fix local endpoint accounting
https://git.kernel.org/netdev/net/c/843b5e75efff
- [net,7/7] mptcp: update MIB_RMSUBFLOW in cmd_sf_destroy
https://git.kernel.org/netdev/net/c/d2d21f175f1f
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-07-06 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 21:32 [PATCH net 0/7] mptcp: Path manager fixes for 5.19 Mat Martineau
2022-07-05 21:32 ` [PATCH net 1/7] mptcp: fix locking in mptcp_nl_cmd_sf_destroy() Mat Martineau
2022-07-05 21:32 ` [PATCH net 2/7] mptcp: Avoid acquiring PM lock for subflow priority changes Mat Martineau
2022-07-05 21:32 ` [PATCH net 3/7] mptcp: Acquire the subflow socket lock before modifying MP_PRIO flags Mat Martineau
2022-07-05 21:32 ` [PATCH net 4/7] mptcp: netlink: issue MP_PRIO signals from userspace PMs Mat Martineau
2022-07-05 21:32 ` [PATCH net 5/7] selftests: mptcp: userspace PM support for MP_PRIO signals Mat Martineau
2022-07-05 21:32 ` [PATCH net 6/7] mptcp: fix local endpoint accounting Mat Martineau
2022-07-05 21:32 ` [PATCH net 7/7] mptcp: update MIB_RMSUBFLOW in cmd_sf_destroy Mat Martineau
2022-07-06 1:00 ` [PATCH net 0/7] mptcp: Path manager fixes for 5.19 Jakub Kicinski
2022-07-06 17:14 ` Mat Martineau
2022-07-06 20:20 ` Jakub Kicinski
2022-07-06 12: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=165710882054.23384.2979823140272634407.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