From: Stephen Hemminger <stephen@networkplumber.org>
To: maxime.coquelin@redhat.com, tiwei.bie@intel.com, zhihong.wang@intel.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: [dpdk-dev] [PATCH 1/2] net/netvsc: fix lgtm static checker complaint
Date: Wed, 27 Mar 2019 14:08:42 -0700 [thread overview]
Message-ID: <20190327210843.13813-2-stephen@networkplumber.org> (raw)
Message-ID: <20190327210842.2xhL0qvFCOz_VT5INAGrycrBkficIOJl0TC8AYnMtrI@z> (raw)
In-Reply-To: <20190327210843.13813-1-stephen@networkplumber.org>
Since previous test is for mtu < 1519 the next else if
is always true. This causes the lgtm static tool to complain.
Not a real issue, just cosmetic.
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
---
drivers/net/netvsc/hn_rxtx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/netvsc/hn_rxtx.c b/drivers/net/netvsc/hn_rxtx.c
index 6197118b01ee..8818d68cea5c 100644
--- a/drivers/net/netvsc/hn_rxtx.c
+++ b/drivers/net/netvsc/hn_rxtx.c
@@ -123,7 +123,7 @@ hn_update_packet_stats(struct hn_stats *stats, const struct rte_mbuf *m)
stats->size_bins[0]++;
else if (s < 1519)
stats->size_bins[6]++;
- else if (s >= 1519)
+ else
stats->size_bins[7]++;
}
--
2.17.1
next prev parent reply other threads:[~2019-03-27 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 21:08 [dpdk-dev] [PATCH 0/2] minor lgtm warning fixes Stephen Hemminger
2019-03-27 21:08 ` Stephen Hemminger
2019-03-27 21:08 ` Stephen Hemminger [this message]
2019-03-27 21:08 ` [dpdk-dev] [PATCH 1/2] net/netvsc: fix lgtm static checker complaint Stephen Hemminger
2019-03-28 0:25 ` Rami Rosen
2019-03-28 0:25 ` Rami Rosen
2019-03-27 21:08 ` [dpdk-dev] [PATCH 2/2] net/virtio: " Stephen Hemminger
2019-03-27 21:08 ` Stephen Hemminger
2019-03-28 0:28 ` Rami Rosen
2019-03-28 0:28 ` Rami Rosen
2019-03-28 11:04 ` Maxime Coquelin
2019-03-28 11:04 ` Maxime Coquelin
2019-03-28 17:11 ` [dpdk-dev] [PATCH 0/2] minor lgtm warning fixes Ferruh Yigit
2019-03-28 17:11 ` Ferruh Yigit
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=20190327210843.13813-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tiwei.bie@intel.com \
--cc=zhihong.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 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).