MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v1 0/6] BPF path manager, part 4
Date: Mon, 24 Feb 2025 12:05:11 +0100	[thread overview]
Message-ID: <dcd5cd26-03d6-4b8e-bd60-c27c7ed07497@kernel.org> (raw)
In-Reply-To: <cover.1740384564.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 24/02/2025 09:13, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> Some path manager related refactoring and cleanups.
> 
> Geliang Tang (6):
>   mptcp: pm: in-kernel: avoid access entry without lock
>   mptcp: pm: in-kernel: reduce parameters of set_flags
>   mptcp: pm: use addr entry for get_local_id

For these 3 patches above:

Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>

>   mptcp: pm: in-kernel: use kmemdup helper
>   sock: add sock_kmemdup helper
>   mptcp: pm: userspace: use sock_kmemdup helper
> 
>  include/net/sock.h       |  1 +
>  net/core/sock.c          | 23 +++++++++++++++++++++++
>  net/mptcp/pm.c           |  9 ++++++---
>  net/mptcp/pm_netlink.c   | 30 +++++++++++++-----------------
>  net/mptcp/pm_userspace.c | 20 +++++++-------------
>  net/mptcp/protocol.h     |  6 ++++--
>  6 files changed, 54 insertions(+), 35 deletions(-)
Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  parent reply	other threads:[~2025-02-24 11:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24  8:13 [PATCH mptcp-next v1 0/6] BPF path manager, part 4 Geliang Tang
2025-02-24  8:13 ` [PATCH mptcp-next v1 1/6] mptcp: pm: in-kernel: avoid access entry without lock Geliang Tang
2025-02-24  8:31   ` Matthieu Baerts
2025-02-24 11:02     ` Matthieu Baerts
2025-02-24  8:13 ` [PATCH mptcp-next v1 2/6] mptcp: pm: in-kernel: reduce parameters of set_flags Geliang Tang
2025-02-24  8:13 ` [PATCH mptcp-next v1 3/6] mptcp: pm: use addr entry for get_local_id Geliang Tang
2025-02-24  8:13 ` [PATCH mptcp-next v1 4/6] mptcp: pm: in-kernel: use kmemdup helper Geliang Tang
2025-02-24  8:13 ` [PATCH mptcp-next v1 5/6] sock: add sock_kmemdup helper Geliang Tang
2025-02-24  8:54   ` Matthieu Baerts
2025-02-24 10:42     ` Geliang Tang
2025-02-24 10:59       ` Matthieu Baerts
2025-02-24  8:13 ` [PATCH mptcp-next v1 6/6] mptcp: pm: userspace: use " Geliang Tang
2025-02-24  9:22 ` [PATCH mptcp-next v1 0/6] BPF path manager, part 4 MPTCP CI
2025-02-24 11:05 ` Matthieu Baerts [this message]
2025-02-26 16:29   ` Matthieu Baerts

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=dcd5cd26-03d6-4b8e-bd60-c27c7ed07497@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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