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/2] mptcp: pm: lockless list traversal and cleanup
Date: Tue, 19 Nov 2024 04:00:43 +0000 [thread overview]
Message-ID: <173198884352.97799.1737627825332928151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241115-net-next-mptcp-pm-lockless-dump-v1-0-f4a1bcb4ca2c@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 15 Nov 2024 17:52:33 +0100 you wrote:
> Here are two patches improving the MPTCP in-kernel path-manager.
>
> - Patch 1: the get and dump endpoints operations are iterating over the
> endpoints list in a lockless way.
>
> - Patch 2: reduce the code duplication to lookup an endpoint.
>
> [...]
Here is the summary with links:
- [net-next,1/2] mptcp: pm: lockless list traversal to dump endp
https://git.kernel.org/netdev/net-next/c/3fbb27b7f87e
- [net-next,2/2] mptcp: pm: avoid code duplication to lookup endp
https://git.kernel.org/netdev/net-next/c/1d7fa6ceb91f
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-11-19 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 16:52 [PATCH net-next 0/2] mptcp: pm: lockless list traversal and cleanup Matthieu Baerts (NGI0)
2024-11-15 16:52 ` [PATCH net-next 1/2] mptcp: pm: lockless list traversal to dump endp Matthieu Baerts (NGI0)
2024-11-15 16:52 ` [PATCH net-next 2/2] mptcp: pm: avoid code duplication to lookup endp Matthieu Baerts (NGI0)
2024-11-19 4: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=173198884352.97799.1737627825332928151.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.