mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: 13145886936@163.com, roopa@nvidia.com, nikolay@nvidia.com,
	davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	gushengxian <gushengxian@yulong.com>
Subject: Re: [PATCH] net: bridge: remove redundant return
Date: Wed, 23 Jun 2021 12:51:52 +0200	[thread overview]
Message-ID: <e8df63b4-b16b-c3ed-3991-508c5840cf8d@gmail.com> (raw)
In-Reply-To: <20210623005307.6215-1-13145886936@163.com>



On 6/23/21 2:53 AM, 13145886936@163.com wrote:
> From: gushengxian <gushengxian@yulong.com>
> 
> Return statements are not needed in Void function.

Maybe, but this just works.

I see your patch as a matter of taste.


> 
> Signed-off-by: gushengxian <gushengxian@yulong.com>
> ---
>  net/bridge/br_netlink.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c
> index 8642e56059fb..b70075939721 100644
> --- a/net/bridge/br_netlink.c
> +++ b/net/bridge/br_netlink.c
> @@ -619,7 +619,7 @@ void br_ifinfo_notify(int event, const struct net_bridge *br,
>  {
>  	u32 filter = RTEXT_FILTER_BRVLAN_COMPRESSED;
>  
> -	return br_info_notify(event, br, port, filter);
> +	br_info_notify(event, br, port, filter);
>  }
>  
>  /*
> @@ -814,7 +814,7 @@ static const struct nla_policy br_port_policy[IFLA_BRPORT_MAX + 1] = {
>  	[IFLA_BRPORT_MODE]	= { .type = NLA_U8 },
>  	[IFLA_BRPORT_GUARD]	= { .type = NLA_U8 },
>  	[IFLA_BRPORT_PROTECT]	= { .type = NLA_U8 },
> -	[IFLA_BRPORT_FAST_LEAVE]= { .type = NLA_U8 },
> +	[IFLA_BRPORT_FAST_LEAVE] = { .type = NLA_U8 },

Useless noise.

>  	[IFLA_BRPORT_LEARNING]	= { .type = NLA_U8 },
>  	[IFLA_BRPORT_UNICAST_FLOOD] = { .type = NLA_U8 },
>  	[IFLA_BRPORT_PROXYARP]	= { .type = NLA_U8 },
> 

      reply	other threads:[~2021-06-23 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  0:53 13145886936
2021-06-23 10:51 ` Eric Dumazet [this message]

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=e8df63b4-b16b-c3ed-3991-508c5840cf8d@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=13145886936@163.com \
    --cc=davem@davemloft.net \
    --cc=gushengxian@yulong.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.com \
    /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

all inboxes | Powered by JetHome®