From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Helin Zhang <helin.zhang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>, wei.zhao1@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fix duplicated check
Date: Thu, 13 Apr 2017 10:48:52 +0100 [thread overview]
Message-ID: <4de91546-a77f-750e-9acf-1e9ebc5ddf8a@intel.com> (raw)
In-Reply-To: <20170411152034.23784-1-ferruh.yigit@intel.com>
On 4/11/2017 4:20 PM, Ferruh Yigit wrote:
> Same check duplicated, updated check according what commend states.
>
> Coverity issue: 1407507
> Fixes: 11777435c727 ("net/ixgbe: parse flow director filter")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Superseded by http://dpdk.org/dev/patchwork/patch/23606/
next prev parent reply other threads:[~2017-04-13 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 15:20 Ferruh Yigit
2017-04-13 9:48 ` Ferruh Yigit [this message]
2017-04-14 3:52 ` Zhao1, Wei
2017-04-14 9:04 ` Ferruh Yigit
2017-04-14 9:06 ` Zhao1, Wei
2017-04-14 9:08 ` Ferruh Yigit
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=4de91546-a77f-750e-9acf-1e9ebc5ddf8a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=wei.zhao1@intel.com \
--cc=wenzhuo.lu@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).