From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/3 v3] bnxt: use appropriate data type in bnxt_alloc_vnic_attributes
Date: Mon, 07 Nov 2016 19:35:48 +0100 [thread overview]
Message-ID: <2105407.VUx41MYxrN@xps13> (raw)
In-Reply-To: <20161107151204.GA24819@C02PT1RBG8WP.wifi.aus.avagotech.net>
2016-11-07 09:12, Ajit Khaparde:
> Prevent the arithmetic in bnxt_alloc_vnic_attributes from causing
> any unintentional havoc because of the usage of a signed variable.
>
> Coverity: 137874
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Series applied, thanks
As a regular contributor, please follow the contribution guidelines:
http://dpdk.org/dev#send
prev parent reply other threads:[~2016-11-07 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 18:58 [dpdk-dev] [PATCH 1/2 v2] " Ajit Khaparde
2016-11-04 10:52 ` Ferruh Yigit
2016-11-04 17:35 ` Ajit Khaparde
2016-11-04 19:11 ` [dpdk-dev] [PATCH 1/3 v3] " Ajit Khaparde
2016-11-07 15:12 ` Ajit Khaparde
2016-11-07 18:35 ` Thomas Monjalon [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=2105407.VUx41MYxrN@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).