All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliangtang@gmail.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, Jenkins Tessares <kernel-dev@tessares.net>,
	 kernel test robot <lkp@intel.com>
Subject: Re: [PATCH mptcp-next] Squash to "mptcp: remote addresses fullmesh"
Date: Wed, 4 Aug 2021 19:31:05 +0800	[thread overview]
Message-ID: <CA+WQbwvhXX+T+tm2G9Jyi67Pd4sXDfhUn3dgKL_5eQ014tD8gw@mail.gmail.com> (raw)
In-Reply-To: <20210804073710.681267-1-matthieu.baerts@tessares.net>

Hi Matt,

Thanks for fixing this.

Acked-by: Geliang Tang <geliangtang@xiaomi.com>

-Geliang

Matthieu Baerts <matthieu.baerts@tessares.net> 于2021年8月4日周三 下午3:37写道:
>
> This fixes 'unused-but-set-variable' warning.
>
> Jenkins Tessares reported [1] this error:
>
>   net/mptcp/pm_netlink.c: In function 'fill_remote_addresses_vec':
>   net/mptcp/pm_netlink.c:435:23: error: variable 'pernet' set but not  used [-Werror=unused-but-set-variable]
>     435 |  struct pm_nl_pernet *pernet;
>         |                       ^~~~~~
>   cc1: all warnings being treated as errors
>
> Indeed, this variable is defined and set but not used. We can remove it.
>
> [1] https://github.com/multipath-tcp/mptcp_net-next/actions/runs/1096568275
>
> Reported-by: Jenkins Tessares <kernel-dev@tessares.net>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> ---
>
> Notes:
>     to be squashed in "mptcp: remote addresses fullmesh"
>
>  net/mptcp/pm_netlink.c | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> index cbef50fff6e8..29ff454411b1 100644
> --- a/net/mptcp/pm_netlink.c
> +++ b/net/mptcp/pm_netlink.c
> @@ -432,11 +432,9 @@ static unsigned int fill_remote_addresses_vec(struct mptcp_sock *msk, bool fullm
>         struct sock *sk = (struct sock *)msk, *ssk;
>         struct mptcp_subflow_context *subflow;
>         struct mptcp_addr_info remote = { 0 };
> -       struct pm_nl_pernet *pernet;
>         unsigned int subflows_max;
>         int i = 0;
>
> -       pernet = net_generic(sock_net(sk), pm_nl_pernet_id);
>         subflows_max = mptcp_pm_get_subflows_max(msk);
>
>         /* Non-fullmesh endpoint, fill in the single entry
> --
> 2.31.1
>
>

  reply	other threads:[~2021-08-04 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  7:37 [PATCH mptcp-next] Squash to "mptcp: remote addresses fullmesh" Matthieu Baerts
2021-08-04 11:31 ` Geliang Tang [this message]
2021-08-04 13:06   ` 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=CA+WQbwvhXX+T+tm2G9Jyi67Pd4sXDfhUn3dgKL_5eQ014tD8gw@mail.gmail.com \
    --to=geliangtang@gmail.com \
    --cc=kernel-dev@tessares.net \
    --cc=lkp@intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    /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.