[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03869802-eb14-ed32-e9d7-53b17a74904f@kernel.org>
Date: Wed, 13 Dec 2023 15:38:18 -0800 (PST)
From: Mat Martineau <martineau@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, donald.hunter@...il.com, matttbe@...nel.org,
dcaratti@...hat.com, mptcp@...ts.linux.dev
Subject: Re: [PATCH net-next 3/3] netlink: specs: mptcp: rename the MPTCP
path management(?) spec
On Wed, 13 Dec 2023, Jakub Kicinski wrote:
> We assume in handful of places that the name of the spec is
> the same as the name of the family. We could fix that but
> it seems like a fair assumption to make. Rename the MPTCP
> spec instead.
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> ---
> CC: matttbe@...nel.org
> CC: martineau@...nel.org
> CC: dcaratti@...hat.com
> CC: mptcp@...ts.linux.dev
> ---
> Documentation/netlink/specs/{mptcp.yaml => mptcp_pm.yaml} | 0
> include/uapi/linux/mptcp_pm.h | 2 +-
> net/mptcp/mptcp_pm_gen.c | 2 +-
> net/mptcp/mptcp_pm_gen.h | 2 +-
> 4 files changed, 3 insertions(+), 3 deletions(-)
> rename Documentation/netlink/specs/{mptcp.yaml => mptcp_pm.yaml} (100%)
>
Hi Jakub -
The renaming here is fine. "path management" is the right expansion of
"pm" in this context, so you can remove the "(?)" from the summary line.
Reviewed-by: Mat Martineau <martineau@...nel.org>
Powered by blists - more mailing lists