All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/2] fix coverity reported issues
Date: Wed,  6 May 2020 20:11:34 -0700	[thread overview]
Message-ID: <20200507031136.46035-1-ajit.khaparde@broadcom.com> (raw)
In-Reply-To: <20200505191738.58219-1-ajit.khaparde@broadcom.com>

Fix issues reported by Coverity.
Note that one issue addressed by patch [1/2] was reported in
internal coverity scan.

v1->v2: mention that one of the issue was reported in internal scan.

Ajit Khaparde (1):
  net/bnxt: fix uninitialized variable error

Kishore Padmanabha (1):
  net/bnxt: fix overrun of the ulp device params array

 drivers/net/bnxt/tf_core/tf_tbl.c         | 2 +-
 drivers/net/bnxt/tf_ulp/ulp_template_db.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.21.1 (Apple Git-122.3)


  parent reply	other threads:[~2020-05-07  3:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 19:17 [dpdk-dev] [PATCH 0/2] fix coverity reported issues Ajit Khaparde
2020-05-05 19:17 ` [dpdk-dev] [PATCH 1/2] net/bnxt: fix overrun of the ulp device params array Ajit Khaparde
2020-05-06  9:17   ` Ferruh Yigit
2020-05-06 22:14     ` Ajit Khaparde
2020-05-07  0:09       ` Ferruh Yigit
2020-05-07  3:14         ` Ajit Khaparde
2020-05-05 19:17 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix uninitialized variable error Ajit Khaparde
2020-05-06  9:13   ` Ferruh Yigit
2020-05-07 18:55     ` Ajit Khaparde
2020-05-07 21:15       ` Ferruh Yigit
2020-05-06  1:40 ` [dpdk-dev] [PATCH 0/2] fix coverity reported issues Ajit Khaparde
2020-05-07  3:11 ` Ajit Khaparde [this message]
2020-05-07  3:11   ` [dpdk-dev] [PATCH v2 1/2] net/bnxt: fix overrun of the ulp device params array Ajit Khaparde
2020-05-07  3:11   ` [dpdk-dev] [PATCH v2 2/2] net/bnxt: fix uninitialized variable error Ajit Khaparde

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=20200507031136.46035-1-ajit.khaparde@broadcom.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    /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.