public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Leon Romanovsky <leonro@nvidia.com>, <netdev@vger.kernel.org>,
	Shannon Nelson <shannon.nelson@oracle.com>
Subject: Re: [PATCH ipsec-next] xfrm: delete duplicated functions that calls same xfrm_api_check()
Date: Tue, 1 Feb 2022 08:07:01 +0100	[thread overview]
Message-ID: <20220201070701.GU1223722@gauss3.secunet.de> (raw)
In-Reply-To: <5f9d6820e0548cb3304cbb49bcb84bedb15d7403.1643274380.git.leonro@nvidia.com>

On Thu, Jan 27, 2022 at 11:08:40AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> The xfrm_dev_register() and xfrm_dev_feat_change() have same
> implementation of one call to xfrm_api_check(). Instead of doing such
> indirection, call to xfrm_api_check() directly and delete duplicated
> functions.
> 
> Fixes: 92a2320697f7 ("xfrm: check for xdo_dev_ops add and delete")

There was nothing broken here, just a suboptimal implementation.
So please remove the Fixes tag, otherwise it gets backported
without a need.

Thanks!

> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
>  net/xfrm/xfrm_device.c | 14 ++------------
>  1 file changed, 2 insertions(+), 12 deletions(-)
> 
> diff --git a/net/xfrm/xfrm_device.c b/net/xfrm/xfrm_device.c
> index 3fa066419d37..36d6c1835844 100644
> --- a/net/xfrm/xfrm_device.c
> +++ b/net/xfrm/xfrm_device.c
> @@ -380,16 +380,6 @@ static int xfrm_api_check(struct net_device *dev)
>  	return NOTIFY_DONE;
>  }
>  
> -static int xfrm_dev_register(struct net_device *dev)
> -{
> -	return xfrm_api_check(dev);
> -}
> -
> -static int xfrm_dev_feat_change(struct net_device *dev)
> -{
> -	return xfrm_api_check(dev);
> -}
> -
>  static int xfrm_dev_down(struct net_device *dev)
>  {
>  	if (dev->features & NETIF_F_HW_ESP)
> @@ -404,10 +394,10 @@ static int xfrm_dev_event(struct notifier_block *this, unsigned long event, void
>  
>  	switch (event) {
>  	case NETDEV_REGISTER:
> -		return xfrm_dev_register(dev);
> +		return xfrm_api_check(dev);
>  
>  	case NETDEV_FEAT_CHANGE:
> -		return xfrm_dev_feat_change(dev);
> +		return xfrm_api_check(dev);
>  
>  	case NETDEV_DOWN:
>  	case NETDEV_UNREGISTER:
> -- 
> 2.34.1

  reply	other threads:[~2022-02-01  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  9:08 [PATCH ipsec-next] xfrm: delete duplicated functions that calls same xfrm_api_check() Leon Romanovsky
2022-02-01  7:07 ` Steffen Klassert [this message]
2022-02-01  7:31   ` Leon Romanovsky

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=20220201070701.GU1223722@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@oracle.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