DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hernan Vargas <hernan.vargas@intel.com>,
	dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com, john.mcnamara@intel.com
Subject: Re: [PATCH v3 0/3] DPDK Coverity issue 381631, 381646
Date: Thu, 23 Feb 2023 10:29:02 +0100	[thread overview]
Message-ID: <d6c7c190-58ad-9fc8-e1e9-ac4ca93b86bc@redhat.com> (raw)
In-Reply-To: <20230222164043.170909-1-hernan.vargas@intel.com>



On 2/22/23 17:40, Hernan Vargas wrote:
> v3: Split commits further for clarity.
> 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 (3):
>    baseband/acc: fix check after deref and dead code
>    baseband/acc: remove unused ops check
>    baseband/acc: add check for empty queue
> 
>   drivers/baseband/acc/rte_acc100_pmd.c | 7 ++-----
>   1 file changed, 2 insertions(+), 5 deletions(-)
> 

Applied to dpdk-next-baseband/for-main.

Thanks,
Maxime


      parent reply	other threads:[~2023-02-23  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 16:40 Hernan Vargas
2023-02-22 16:40 ` [PATCH v3 1/3] baseband/acc: fix check after deref and dead code Hernan Vargas
2023-02-22 16:40 ` [PATCH v3 2/3] baseband/acc: remove unused ops check Hernan Vargas
2023-02-22 17:55   ` Maxime Coquelin
2023-02-22 16:40 ` [PATCH v3 3/3] baseband/acc: add check for empty queue Hernan Vargas
2023-02-22 17:55   ` Maxime Coquelin
2023-02-23  9:29 ` Maxime Coquelin [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=d6c7c190-58ad-9fc8-e1e9-ac4ca93b86bc@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.com \
    --cc=john.mcnamara@intel.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).