DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix issues for RSS flow API
Date: Thu, 25 Jan 2018 06:12:01 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611531338B6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180123064302.118082-1-wei.zhao1@intel.com>



> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Thursday, January 25, 2018 12:00 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Subject: RE: [PATCH] net/i40e: fix issues for RSS flow API
> 
> > -----Original Message-----
> > From: Zhao1, Wei
> > Sent: Tuesday, January 23, 2018 2:43 PM
> > To: dev@dpdk.org
> > Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Zhao1, Wei
> <wei.zhao1@intel.com>
> > Subject: [PATCH] net/i40e: fix issues for RSS flow API
> >
> > This patch fix issues check from DPDK coverity issues.
> >
> > Fixes: ecad87d22383e ("net/i40e: move RSS to flow API") Coverity issues:
> > 257020 257024 257037
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> 
> Acked-by Qi Zhang <qi.z.zhang@intel.com>

Nacked-by Qi Zhang <qi.z.zhang@intel.com> since new issue is found, v2 is required.

  parent reply	other threads:[~2018-01-25  6:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  6:43 Wei Zhao
2018-01-25  3:59 ` Zhang, Qi Z
2018-01-25  5:40 ` Zhang, Qi Z
2018-01-26  3:17   ` Zhao1, Wei
2018-01-26  8:32     ` Zhang, Helin
2018-01-26  8:56       ` Zhao1, Wei
2018-01-25  6:12 ` Zhang, Qi Z [this message]
2018-01-25  6:22   ` Zhao1, Wei
2018-01-26  3:08 ` [dpdk-dev] [PATCH v2] net/i40e: fix issue " Wei Zhao
2018-01-26  7:32   ` Zhang, Qi Z
2018-01-26  8:43   ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-01-26  8:46   ` Wei Zhao
2018-01-30  2:46     ` Zhang, Helin

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=039ED4275CED7440929022BC67E70611531338B6@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=wei.zhao1@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).