From: Hernan Vargas <hernan.vargas@intel.com>
To: dev@dpdk.org, maxime.coquelin@redhat.com, gakhil@marvell.com,
trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com,
john.mcnamara@intel.com, Hernan Vargas <hernan.vargas@intel.com>
Subject: [PATCH v2 0/2] DPDK Coverity issue 381631, 381646
Date: Tue, 7 Feb 2023 17:59:59 -0800 [thread overview]
Message-ID: <20230208020001.181055-1-hernan.vargas@intel.com> (raw)
v2: Split code unrelated to coverity fix in separate commit.
v1: Upstream fix to 23.03 for potential issue of dereferencing a pointer before null check.
Hernan Vargas (2):
baseband/acc: fix check after deref and dead code
baseband/acc: add check for empty queue
drivers/baseband/acc/rte_acc100_pmd.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
--
2.37.1
next reply other threads:[~2023-02-08 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 1:59 Hernan Vargas [this message]
2023-02-08 2:00 ` [PATCH v2 1/2] baseband/acc: fix check after deref and dead code Hernan Vargas
2023-02-20 15:37 ` Maxime Coquelin
2023-02-08 2:00 ` [PATCH v2 2/2] baseband/acc: add check for empty queue Hernan Vargas
2023-02-20 15:37 ` Maxime Coquelin
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=20230208020001.181055-1-hernan.vargas@intel.com \
--to=hernan.vargas@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=trix@redhat.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).