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 v7 04/11] mptcp: sysctl: add available_path_managers
Date: Mon, 3 Mar 2025 11:41:00 +0100 [thread overview]
Message-ID: <51e3640e-3131-4e40-89dd-192855c46c8a@kernel.org> (raw)
In-Reply-To: <4af75cf9a0ebfef70ca6151d05624b8d5abc723b.1740975633.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 03/03/2025 05:22, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Similarly to net.mptcp.available_schedulers, this patch adds a new one
> net.mptcp.available_path_managers to list the available path mangers.
Detail: s/mangers/managers/
("manger" means "to eat" in French, so that looks strange to me :) )
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-03-03 10:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 4:22 [PATCH mptcp-next v7 00/11] BPF path manager, part 5 Geliang Tang
2025-03-03 4:22 ` [PATCH mptcp-next v7 01/11] mptcp: pm: define struct mptcp_pm_ops Geliang Tang
2025-03-03 10:39 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 02/11] mptcp: sysctl: new sysctl to set path manager by name Geliang Tang
2025-03-03 10:40 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 03/11] mptcp: sysctl: map pm_type to path_manager Geliang Tang
2025-03-03 10:40 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 04/11] mptcp: sysctl: add available_path_managers Geliang Tang
2025-03-03 10:41 ` Matthieu Baerts [this message]
2025-03-03 4:22 ` [PATCH mptcp-next v7 05/11] mptcp: pm: in-kernel: register mptcp_kernel_pm Geliang Tang
2025-03-03 10:42 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 06/11] mptcp: pm: userspace: register mptcp_userspace_pm Geliang Tang
2025-03-03 10:52 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 07/11] mptcp: pm: initialize and release mptcp_pm_ops Geliang Tang
2025-03-03 10:53 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 08/11] mptcp: pm: drop pm_type in mptcp_pm_data Geliang Tang
2025-03-03 10:57 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 09/11] mptcp: sysctl: drop get_pm_type helper Geliang Tang
2025-03-03 10:57 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 10/11] mptcp: pm: make get_local_id helpers static Geliang Tang
2025-03-03 10:58 ` Matthieu Baerts
2025-03-03 4:22 ` [PATCH mptcp-next v7 11/11] mptcp: pm: make is_backup " Geliang Tang
2025-03-03 5:32 ` [PATCH mptcp-next v7 00/11] BPF path manager, part 5 MPTCP CI
2025-03-03 10:38 ` 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=51e3640e-3131-4e40-89dd-192855c46c8a@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