From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Miller <john.miller@atomicrules.com>, dev@dpdk.org
Cc: ed.czeck@atomicrules.com, shepard.siegel@atomicrules.com
Subject: Re: [dpdk-dev] [PATCH 1/4] net/ark: fix for buffer not null terminated
Date: Tue, 16 May 2017 17:37:07 +0100 [thread overview]
Message-ID: <40253da3-0b35-7414-a33e-639637f6d4e1@intel.com> (raw)
In-Reply-To: <1494951258-11232-1-git-send-email-john.miller@atomicrules.com>
On 5/16/2017 5:14 PM, John Miller wrote:
> Coverity issue: 144512
> Coverity issue: 144513
> Fixes: 9c7188a68d7b ("net/ark: provide API for hardware modules pktchkr and pktgen")
>
> Signed-off-by: John Miller <john.miller@atomicrules.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-05-16 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 16:14 John Miller
2017-05-16 16:14 ` [dpdk-dev] [PATCH 2/4] net/ark: fix return code not checked John Miller
2017-05-16 16:14 ` [dpdk-dev] [PATCH 3/4] net/ark: fix null pointer dereference John Miller
2017-05-16 16:14 ` [dpdk-dev] [PATCH 4/4] net/ark: fix return value of null not checked John Miller
2017-05-16 16:37 ` Ferruh Yigit [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=40253da3-0b35-7414-a33e-639637f6d4e1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).