From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Fu, Qi" <qi.fu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Fu, Qi" <qi.fu@intel.com>, "Lin, Xueqin" <xueqin.lin@intel.com>,
"Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH V3]test_plans: add test plan for cvl supporting ecpri protocol
Date: Wed, 3 Mar 2021 05:14:48 +0000 [thread overview]
Message-ID: <a121e3c5c0d44efdbf048913048ab0f7@intel.com> (raw)
In-Reply-To: <20210302162049.229166-1-qi.fu@intel.com>
> dpdk can support ecpri in CVL with wireless pkg, add test plan to cover 3 parts:
> 1. UDP dst port dynamically config for eCPRI.
> 2. RSS supporting for eCPRI.
> 3. FDIR supporting for eCPRI.
>
> Signed-off-by: qifu <qi.fu@intel.com>
> Signed-off-by: Xueqin Lin<xueqin.lin@intel.com>
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
Applied, thanks
prev parent reply other threads:[~2021-03-03 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 16:20 qifu
2021-03-03 5:14 ` Tu, Lijuan [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=a121e3c5c0d44efdbf048913048ab0f7@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=qi.fu@intel.com \
--cc=xueqin.lin@intel.com \
--cc=yuan.peng@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).