From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Junfeng Guo <junfeng.guo@intel.com>,
qi.z.zhang@intel.com, jingjing.wu@intel.com,
beilei.xing@intel.com
Cc: dev@dpdk.org, simei.su@intel.com, yahui.cao@intel.com
Subject: Re: [dpdk-dev] [PATCH 4/5] net/iavf: support eCPRI MSG TYPE 0 for AVF FDIR
Date: Tue, 5 Jan 2021 12:30:07 +0000 [thread overview]
Message-ID: <c6b597e9-91a5-5ddc-9f58-dfd38cfb9c3d@intel.com> (raw)
In-Reply-To: <20201214064913.2306802-5-junfeng.guo@intel.com>
On 12/14/2020 6:49 AM, Junfeng Guo wrote:
> For eCPRI MSG Type 0, ecpriRtcid/ecpriPcid field within the eCPRI
> header will be extracted to Field Vector for AVF FDIR.
>
> SPEC for eCPRI:
> http://www.cpri.info/downloads/eCPRI_v_2.0_2019_05_10c.pdf
>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
fixed following checkpatch warning while merging:
CHECK:LOGICAL_CONTINUATIONS: Logical continuations should be on the previous line
#121: FILE: drivers/net/iavf/iavf_fdir.c:928:
+ if (ecpri_common.type == RTE_ECPRI_MSG_TYPE_IQ_DATA
+ && ecpri_mask->hdr.type0.pc_id == UINT16_MAX) {
next prev parent reply other threads:[~2021-01-05 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 6:49 [dpdk-dev] [PATCH 0/5] support eCPRI MSG TYPE 0 for AVF FDIR and RSS Junfeng Guo
2020-12-14 6:49 ` [dpdk-dev] [PATCH 1/5] common/iavf: add proto hdr flds support for eCPRI Junfeng Guo
2020-12-14 6:49 ` [dpdk-dev] [PATCH 2/5] net/iavf: support flow patterns " Junfeng Guo
2020-12-14 6:49 ` [dpdk-dev] [PATCH 3/5] net/iavf: define new bits " Junfeng Guo
2021-01-05 12:28 ` Ferruh Yigit
2020-12-14 6:49 ` [dpdk-dev] [PATCH 4/5] net/iavf: support eCPRI MSG TYPE 0 for AVF FDIR Junfeng Guo
2021-01-05 12:30 ` Ferruh Yigit [this message]
2020-12-14 6:49 ` [dpdk-dev] [PATCH 5/5] net/iavf: support eCPRI MSG TYPE 0 for RSS Junfeng Guo
2020-12-23 11:07 ` [dpdk-dev] [PATCH 0/5] support eCPRI MSG TYPE 0 for AVF FDIR and RSS Zhang, Qi Z
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=c6b597e9-91a5-5ddc-9f58-dfd38cfb9c3d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=simei.su@intel.com \
--cc=yahui.cao@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).