From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Joseph, Anoob" <Anoob.Joseph@cavium.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: "Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
"Dwivedi, Ankur" <Ankur.Dwivedi@cavium.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] crypto/octeontx: fix null pointer dereferencing
Date: Mon, 12 Nov 2018 11:45:44 +0000 [thread overview]
Message-ID: <c349865d-62c5-d2e0-7df3-8d8db78137af@nxp.com> (raw)
In-Reply-To: <SN6PR07MB49111E668156067707B778F3F8C10@SN6PR07MB4911.namprd07.prod.outlook.com>
Hi Anoob,
On 11/12/2018 4:53 PM, Joseph, Anoob wrote:
> Hi Akhil,
>
> You can squash the entire series. Or should I send a revised patch? Either way is fine.
You can send a revised patch with coverity ID and appropriate patch
description for all the issues resolved here.
-Akhil
next prev parent reply other threads:[~2018-11-12 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 15:24 [dpdk-dev] [PATCH 0/3] fixing coverity reported issues Anoob Joseph
2018-11-11 15:24 ` [dpdk-dev] [PATCH 1/3] crypto/octeontx: fix non null terminated string Anoob Joseph
2018-11-11 15:24 ` [dpdk-dev] [PATCH 2/3] crypto/octeontx: fix null pointer dereferencing Anoob Joseph
2018-11-12 11:20 ` Akhil Goyal
2018-11-12 11:23 ` Joseph, Anoob
2018-11-12 11:45 ` Akhil Goyal [this message]
2018-11-11 15:24 ` [dpdk-dev] [PATCH 3/3] " Anoob Joseph
2018-11-12 18:14 ` [dpdk-dev] [PATCH v2] crypto/octeontx: fix coverity issues Anoob Joseph
2018-11-13 10:12 ` Akhil Goyal
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=c349865d-62c5-d2e0-7df3-8d8db78137af@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=Ankur.Dwivedi@cavium.com \
--cc=Anoob.Joseph@cavium.com \
--cc=Jerin.JacobKollanukkaran@cavium.com \
--cc=NarayanaPrasad.Athreya@cavium.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).