From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nikhil Rao <nikhil.rao@intel.com>, jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] eventdev: fix call to strerror in eth Rx adapter
Date: Thu, 29 Nov 2018 08:53:30 +0000 [thread overview]
Message-ID: <b3915612-c5b4-4201-7e3a-59ae14af34ec@intel.com> (raw)
In-Reply-To: <1543478417-30869-1-git-send-email-nikhil.rao@intel.com>
On 11/29/2018 8:00 AM, Nikhil Rao wrote:
> strerror() input parameter should be > 0.
>
> Coverity issue: 302864
> Fixes: 3810ae435783 ("eventdev: add interrupt driven queues to Rx adapter")
> CC: stable@dpdk.org
>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-11-29 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 8:00 [dpdk-dev] " Nikhil Rao
2018-11-29 8:53 ` Ferruh Yigit [this message]
2018-12-01 14:09 ` [dpdk-dev] [dpdk-stable] " Jerin Jacob
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=b3915612-c5b4-4201-7e3a-59ae14af34ec@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nikhil.rao@intel.com \
--cc=stable@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 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).