From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] mptcp: pm: userspace: misc cleanups
Date: Sun, 15 Dec 2024 22:40:30 +0000 [thread overview]
Message-ID: <173430243000.3595979.4122680352068648129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241213-net-next-mptcp-pm-misc-cleanup-v1-0-ddb6d00109a8@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 Dec 2024 20:52:51 +0100 you wrote:
> These cleanups lead the way to the unification of the path-manager
> interfaces, and allow future extensions. The following patches are not
> linked to each others, but are all related to the userspace
> path-manager.
>
> - Patch 1: add a new helper to reduce duplicated code.
>
> [...]
Here is the summary with links:
- [net-next,1/7] mptcp: add mptcp_userspace_pm_lookup_addr helper
https://git.kernel.org/netdev/net-next/c/e7b4083b90b7
- [net-next,2/7] mptcp: add mptcp_for_each_userspace_pm_addr macro
https://git.kernel.org/netdev/net-next/c/a28717d8414e
- [net-next,3/7] mptcp: add mptcp_userspace_pm_get_sock helper
https://git.kernel.org/netdev/net-next/c/6a389c8ceeb7
- [net-next,4/7] mptcp: move mptcp_pm_remove_addrs into pm_userspace
https://git.kernel.org/netdev/net-next/c/8008e77e0741
- [net-next,5/7] mptcp: drop free_list for deleting entries
https://git.kernel.org/netdev/net-next/c/88d097316371
- [net-next,6/7] mptcp: change local addr type of subflow_destroy
https://git.kernel.org/netdev/net-next/c/1c670b39cec7
- [net-next,7/7] mptcp: drop useless "err = 0" in subflow_destroy
https://git.kernel.org/netdev/net-next/c/5409fd6fec68
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:[~2024-12-15 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:52 [PATCH net-next 0/7] mptcp: pm: userspace: misc cleanups Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 1/7] mptcp: add mptcp_userspace_pm_lookup_addr helper Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 2/7] mptcp: add mptcp_for_each_userspace_pm_addr macro Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 3/7] mptcp: add mptcp_userspace_pm_get_sock helper Matthieu Baerts (NGI0)
2024-12-15 22:32 ` Jakub Kicinski
2024-12-13 19:52 ` [PATCH net-next 4/7] mptcp: move mptcp_pm_remove_addrs into pm_userspace Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 5/7] mptcp: drop free_list for deleting entries Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 6/7] mptcp: change local addr type of subflow_destroy Matthieu Baerts (NGI0)
2024-12-13 19:52 ` [PATCH net-next 7/7] mptcp: drop useless "err = 0" in subflow_destroy Matthieu Baerts (NGI0)
2024-12-15 22: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=173430243000.3595979.4122680352068648129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--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).