linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jubran, Samih" <sameehj@amazon.com>
To: Colin King <colin.king@canonical.com>,
	"Belgazal, Netanel" <netanel@amazon.com>,
	"Kiyanovski, Arthur" <akiyano@amazon.com>,
	"Tzalik, Guy" <gtzalik@amazon.com>,
	"Bshara, Saeed" <saeedb@amazon.com>,
	"Machulsky, Zorik" <zorik@amazon.com>,
	"David S . Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] net: ena: ethtool: remove redundant non-zero check on rc
Date: Sun, 23 Feb 2020 08:18:13 +0000	[thread overview]
Message-ID: <0e46020a1433409a8daccb829902280b@EX13D11EUB003.ant.amazon.com> (raw)
In-Reply-To: <20200221232653.33134-1-colin.king@canonical.com>

Ack, Thanks

> -----Original Message-----
> From: Colin King <colin.king@canonical.com>
> Sent: Saturday, February 22, 2020 1:27 AM
> To: Belgazal, Netanel <netanel@amazon.com>; Kiyanovski, Arthur
> <akiyano@amazon.com>; Tzalik, Guy <gtzalik@amazon.com>; Bshara, Saeed
> <saeedb@amazon.com>; Machulsky, Zorik <zorik@amazon.com>; David S .
> Miller <davem@davemloft.net>; Jubran, Samih <sameehj@amazon.com>;
> netdev@vger.kernel.org
> Cc: kernel-janitors@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] net: ena: ethtool: remove redundant non-zero check on rc
> 
> From: Colin Ian King <colin.king@canonical.com>
> 
> The non-zero check on rc is redundant as a previous non-zero check on rc will
> always return and the second check is never reached, hence it is redundant
> and can be removed.  Also remove a blank line.
> 
> Addresses-Coverity: ("Logically dead code")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/net/ethernet/amazon/ena/ena_ethtool.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/net/ethernet/amazon/ena/ena_ethtool.c
> b/drivers/net/ethernet/amazon/ena/ena_ethtool.c
> index ced1d577b62a..1e38930353f2 100644
> --- a/drivers/net/ethernet/amazon/ena/ena_ethtool.c
> +++ b/drivers/net/ethernet/amazon/ena/ena_ethtool.c
> @@ -674,7 +674,6 @@ static int ena_get_rxfh(struct net_device *netdev,
> u32 *indir, u8 *key,
>  	 * supports getting/setting the hash function.
>  	 */
>  	rc = ena_com_get_hash_function(adapter->ena_dev, &ena_func,
> key);
> -
>  	if (rc) {
>  		if (rc == -EOPNOTSUPP) {
>  			key = NULL;
> @@ -685,9 +684,6 @@ static int ena_get_rxfh(struct net_device *netdev,
> u32 *indir, u8 *key,
>  		return rc;
>  	}
> 
> -	if (rc)
> -		return rc;
> -
>  	switch (ena_func) {
>  	case ENA_ADMIN_TOEPLITZ:
>  		func = ETH_RSS_HASH_TOP;
> --
> 2.25.0


  reply	other threads:[~2020-02-23  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 23:26 [PATCH] net: ena: ethtool: remove redundant non-zero check on rc Colin King
2020-02-23  8:18 ` Jubran, Samih [this message]
2020-02-24  0:41 ` David Miller

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=0e46020a1433409a8daccb829902280b@EX13D11EUB003.ant.amazon.com \
    --to=sameehj@amazon.com \
    --cc=akiyano@amazon.com \
    --cc=colin.king@canonical.com \
    --cc=davem@davemloft.net \
    --cc=gtzalik@amazon.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedb@amazon.com \
    --cc=zorik@amazon.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;
as well as URLs for NNTP newsgroup(s).