All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Shougang Wang <shougangx.wang@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: fix coverity issue
Date: Tue, 11 Feb 2020 19:49:11 +0800	[thread overview]
Message-ID: <20200211114911.GL80720@intel.com> (raw)
In-Reply-To: <20200211092622.20667-1-shougangx.wang@intel.com>

On 02/11, Shougang Wang wrote:
>This patch fixes (Logically dead code ) coverity issue.
>
>Coverity issue: 353624
>Fixes: ba7b12dd64e4 ("net/ixgbe: fix link up in FreeBSD")
>
>Signed-off-by: Shougang Wang <shougangx.wang@intel.com>
>---
> drivers/net/ixgbe/ixgbe_ethdev.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
>diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
>index 7ea1962f6..2a248a3f2 100644
>--- a/drivers/net/ixgbe/ixgbe_ethdev.c
>+++ b/drivers/net/ixgbe/ixgbe_ethdev.c
>@@ -4128,13 +4128,10 @@ static int
> ixgbe_wait_for_link_up(struct ixgbe_hw *hw)
> {
> #ifdef RTE_EXEC_ENV_FREEBSD
>-	const int nb_iter = 25;
>-#else
>-	const int nb_iter = 0;
>-#endif
> 	int err, i;
> 	bool link_up = false;
> 	uint32_t speed = 0;
>+	const int nb_iter = 25;
> 
> 	for (i = 0; i < nb_iter; i++) {
> 		err = ixgbe_check_link(hw, &speed, &link_up, 0);
>@@ -4144,7 +4141,12 @@ ixgbe_wait_for_link_up(struct ixgbe_hw *hw)
> 			return 0;
> 		msec_delay(200);
> 	}
>+
>+	return 0;
>+#else
>+	RTE_SET_USED(hw);
> 	return 0;
>+#endif
> }
> 
> /* return 0 means link status changed, -1 means not changed */
>-- 
>2.17.1
>

Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>


Applied to dpdk-next-net-intel, Thanks.

      reply	other threads:[~2020-02-11 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  7:13 [dpdk-dev] [PATCH] net/ixgbe: fix coverity issue Shougang Wang
2020-02-11  8:27 ` Ye Xiaolong
2020-02-11  9:26 ` [dpdk-dev] [PATCH v2] " Shougang Wang
2020-02-11 11:49   ` Ye Xiaolong [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=20200211114911.GL80720@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=shougangx.wang@intel.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 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.