From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
geliang.tang@suse.com
Subject: Re: [PATCH net-next 0/4] mptcp: unify PM interfaces
Date: Sat, 10 Jun 2023 07:12:15 +0000 [thread overview]
Message-ID: <168638113595.4960.8012275935135904829.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230608-upstream-net-next-20230608-mptcp-unify-pm-interfaces-v1-0-b301717c9ff5@tessares.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 08 Jun 2023 15:20:48 +0200 you wrote:
> These patches from Geliang better isolate the two MPTCP path-managers by
> avoiding calling userspace PM functions from the in-kernel PM. Instead,
> new functions declared in pm.c directly dispatch to the right PM.
>
> In addition to have a clearer code, this also avoids a bit of duplicated
> checks.
>
> [...]
Here is the summary with links:
- [net-next,1/4] mptcp: export local_address
https://git.kernel.org/netdev/net-next/c/dc886bce753c
- [net-next,2/4] mptcp: unify pm get_local_id interfaces
https://git.kernel.org/netdev/net-next/c/9bbec87ecfe8
- [net-next,3/4] mptcp: unify pm get_flags_and_ifindex_by_id
https://git.kernel.org/netdev/net-next/c/f40be0db0b76
- [net-next,4/4] mptcp: unify pm set_flags interfaces
(no matching commit)
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-06-10 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:20 [PATCH net-next 0/4] mptcp: unify PM interfaces Matthieu Baerts
2023-06-08 13:20 ` [PATCH net-next 1/4] mptcp: export local_address Matthieu Baerts
2023-06-09 11:25 ` Larysa Zaremba
2023-06-08 13:20 ` [PATCH net-next 2/4] mptcp: unify pm get_local_id interfaces Matthieu Baerts
2023-06-09 11:48 ` Larysa Zaremba
2023-06-08 13:20 ` [PATCH net-next 3/4] mptcp: unify pm get_flags_and_ifindex_by_id Matthieu Baerts
2023-06-09 12:02 ` Larysa Zaremba
2023-06-08 13:20 ` [PATCH net-next 4/4] mptcp: unify pm set_flags interfaces Matthieu Baerts
2023-06-09 13:35 ` Larysa Zaremba
2023-06-10 7:12 ` 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=168638113595.4960.8012275935135904829.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@suse.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--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).