From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
"Dai, Wei" <wei.dai@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 2/2] net/ixgbe: move RSS to flow API
Date: Thu, 4 Jan 2018 08:51:32 +0000 [thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C943C2@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E71ACC47A3@SHSMSX103.ccr.corp.intel.com>
The same, a new v4 commit to DPDK.org.
> -----Original Message-----
> From: Zhang, Helin
> Sent: Thursday, December 21, 2017 11:12 AM
> To: Zhao1, Wei <wei.zhao1@intel.com>; Dai, Wei <wei.dai@intel.com>;
> dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v3 2/2] net/ixgbe: move RSS to flow API
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhao1, Wei
> > Sent: Friday, December 8, 2017 10:28 AM
> > To: Dai, Wei; dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v3 2/2] net/ixgbe: move RSS to flow API
> >
> > Hi, daiwei
> > I build the code with ICC for second time, it can pass build and
> > there is no build error.
> > It seems the icc report is not credible.
> >
> > > -----Original Message-----
> > > From: Dai, Wei
> > > Sent: Thursday, December 7, 2017 5:20 PM
> > > To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> > > Cc: Zhao1, Wei <wei.zhao1@intel.com>
> > > Subject: RE: [dpdk-dev] [PATCH v3 2/2] net/ixgbe: move RSS to flow
> > > API
> > >
> > > Hi, Zhao Wei
> > > Please correct build error show in http://dpdk.org/ml/archives/test-
> > > report/2017-November/035130.html
> > >
> > > > -----Original Message-----
> > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Zhao
> > > > Sent: Friday, November 24, 2017 4:05 PM
> > > > To: dev@dpdk.org
> > > > Cc: Zhao1, Wei <wei.zhao1@intel.com>
> > > > Subject: [dpdk-dev] [PATCH v3 2/2] net/ixgbe: move RSS to flow API
> > > >
> > > > Rte_flow actually defined to include RSS, but till now, RSS is out
> > > > of
> > rte_flow.
> > > > This patch is to move ixgbe existing RSS to rte_flow.
> > > >
> > > > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> I think Wei Dai is right, please double check the error reported, and get that
> fixed.
>
> Thanks,
> Helin
next prev parent reply other threads:[~2018-01-04 8:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 9:03 [dpdk-dev] [PATCH 1/2] net/e1000: " Wei Zhao
2017-11-23 9:03 ` [dpdk-dev] [PATCH 2/2] net/ixgbe: " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 0/2] " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 1/2] net/e1000: " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 2/2] net/ixgbe: " Wei Zhao
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 0/2] " Wei Zhao
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 1/2] net/e1000: " Wei Zhao
2017-12-07 9:19 ` Dai, Wei
2017-12-08 2:28 ` Zhao1, Wei
2017-12-21 3:11 ` Zhang, Helin
2018-01-04 8:48 ` Zhao1, Wei
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 2/2] net/ixgbe: " Wei Zhao
2017-12-07 9:19 ` Dai, Wei
2017-12-08 2:27 ` Zhao1, Wei
2017-12-21 3:11 ` Zhang, Helin
2018-01-04 8:51 ` Zhao1, Wei [this message]
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 0/2] " Wei Zhao
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 1/2] net/e1000: " Wei Zhao
2018-01-05 6:05 ` Dai, Wei
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 2/2] net/ixgbe: " Wei Zhao
2018-01-05 6:01 ` Dai, Wei
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 0/2] " Wei Zhao
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 1/2] net/e1000: " Wei Zhao
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 2/2] net/ixgbe: " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 0/2] " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 1/2] net/e1000: " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 2/2] net/ixgbe: " Wei Zhao
2018-01-09 7:11 ` [dpdk-dev] [PATCH v6 0/2] " 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=A2573D2ACFCADC41BB3BE09C6DE313CA07C943C2@PGSMSX103.gar.corp.intel.com \
--to=wei.zhao1@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=wei.dai@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).