MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <martineau@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v12 03/15] mptcp: add token for get-addr in yaml
Date: Thu, 15 Feb 2024 15:00:00 -0800 (PST)	[thread overview]
Message-ID: <6854381a-37e5-347d-7b00-c5e1831227d6@kernel.org> (raw)
In-Reply-To: <4504a86fc813270a21893220297e712e89c4195d.1707910454.git.tanggeliang@kylinos.cn>

On Wed, 14 Feb 2024, Geliang Tang wrote:

> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> This patch adds token paramenter together with addr in get-addr section in

Hi Geliang -

The CI shows a checkpatch warning for the misspelled "parameter" above.

Thanks,

Mat

> mptcp_pm.yaml, then use the following commands to update mptcp_pm_gen.c
> and mptcp_pm_gen.h:
>
> ./tools/net/ynl/ynl-gen-c.py --mode kernel \
>        --spec Documentation/netlink/specs/mptcp_pm.yaml --source \
>        -o net/mptcp/mptcp_pm_gen.c
> ./tools/net/ynl/ynl-gen-c.py --mode kernel \
>        --spec Documentation/netlink/specs/mptcp_pm.yaml --header \
>        -o net/mptcp/mptcp_pm_gen.h
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> Documentation/netlink/specs/mptcp_pm.yaml | 3 ++-
> net/mptcp/mptcp_pm_gen.c                  | 7 ++++---
> net/mptcp/mptcp_pm_gen.h                  | 2 +-
> 3 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/netlink/specs/mptcp_pm.yaml b/Documentation/netlink/specs/mptcp_pm.yaml
> index 49f90cfb4698..af525ed29792 100644
> --- a/Documentation/netlink/specs/mptcp_pm.yaml
> +++ b/Documentation/netlink/specs/mptcp_pm.yaml
> @@ -292,13 +292,14 @@ operations:
>     -
>       name: get-addr
>       doc: Get endpoint information
> -      attribute-set: endpoint
> +      attribute-set: attr
>       dont-validate: [ strict ]
>       flags: [ uns-admin-perm ]
>       do: &get-addr-attrs
>         request:
>           attributes:
>            - addr
> +           - token
>         reply:
>           attributes:
>            - addr
> diff --git a/net/mptcp/mptcp_pm_gen.c b/net/mptcp/mptcp_pm_gen.c
> index 670da7822e6c..c30a2a90a192 100644
> --- a/net/mptcp/mptcp_pm_gen.c
> +++ b/net/mptcp/mptcp_pm_gen.c
> @@ -32,8 +32,9 @@ const struct nla_policy mptcp_pm_del_addr_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1]
> };
>
> /* MPTCP_PM_CMD_GET_ADDR - do */
> -const struct nla_policy mptcp_pm_get_addr_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1] = {
> -	[MPTCP_PM_ENDPOINT_ADDR] = NLA_POLICY_NESTED(mptcp_pm_address_nl_policy),
> +const struct nla_policy mptcp_pm_get_addr_nl_policy[MPTCP_PM_ATTR_TOKEN + 1] = {
> +	[MPTCP_PM_ATTR_ADDR] = NLA_POLICY_NESTED(mptcp_pm_address_nl_policy),
> +	[MPTCP_PM_ATTR_TOKEN] = { .type = NLA_U32, },
> };
>
> /* MPTCP_PM_CMD_FLUSH_ADDRS - do */
> @@ -110,7 +111,7 @@ const struct genl_ops mptcp_pm_nl_ops[11] = {
> 		.doit		= mptcp_pm_nl_get_addr_doit,
> 		.dumpit		= mptcp_pm_nl_get_addr_dumpit,
> 		.policy		= mptcp_pm_get_addr_nl_policy,
> -		.maxattr	= MPTCP_PM_ENDPOINT_ADDR,
> +		.maxattr	= MPTCP_PM_ATTR_TOKEN,
> 		.flags		= GENL_UNS_ADMIN_PERM,
> 	},
> 	{
> diff --git a/net/mptcp/mptcp_pm_gen.h b/net/mptcp/mptcp_pm_gen.h
> index ac9fc7225b6a..e24258f6f819 100644
> --- a/net/mptcp/mptcp_pm_gen.h
> +++ b/net/mptcp/mptcp_pm_gen.h
> @@ -18,7 +18,7 @@ extern const struct nla_policy mptcp_pm_add_addr_nl_policy[MPTCP_PM_ENDPOINT_ADD
>
> extern const struct nla_policy mptcp_pm_del_addr_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1];
>
> -extern const struct nla_policy mptcp_pm_get_addr_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1];
> +extern const struct nla_policy mptcp_pm_get_addr_nl_policy[MPTCP_PM_ATTR_TOKEN + 1];
>
> extern const struct nla_policy mptcp_pm_flush_addrs_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1];
>
> -- 
> 2.40.1
>
>
>

  reply	other threads:[~2024-02-15 23:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 11:39 [PATCH mptcp-next v12 00/15] dump for userspace pm Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 01/15] mptcp: export mptcp_genl_family & mptcp_nl_fill_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 02/15] mptcp: implement mptcp_userspace_pm_dump_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 03/15] mptcp: add token for get-addr in yaml Geliang Tang
2024-02-15 23:00   ` Mat Martineau [this message]
2024-02-14 11:39 ` [PATCH mptcp-next v12 04/15] mptcp: dump addrs in userspace pm list Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 05/15] mptcp: check userspace pm flags Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 06/15] selftests: mptcp: add userspace pm subflow flag Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 07/15] selftests: mptcp: add token for dump_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 08/15] selftests: mptcp: add check_output helper Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 09/15] selftests: mptcp: dump after creating id 0 subflow Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 10/15] selftests: mptcp: dump userspace addrs list Geliang Tang
2024-02-15 22:57   ` Mat Martineau
2024-02-16 10:30     ` Matthieu Baerts
2024-02-14 11:40 ` [PATCH mptcp-next v12 11/15] mptcp: add userspace_pm_lookup_addr_by_id helper Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 12/15] mptcp: implement mptcp_userspace_pm_get_addr Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 13/15] mptcp: get addr in userspace pm list Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 14/15] selftests: mptcp: add token for get_addr Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 15/15] selftests: mptcp: userspace pm get addr tests Geliang Tang
2024-02-14 12:37   ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
2024-02-14 12:48   ` MPTCP CI

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=6854381a-37e5-347d-7b00-c5e1831227d6@kernel.org \
    --to=martineau@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