From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>,
"Zhu, WenhuiX" <wenhuix.zhu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:add not support nic on vlan_qinq_tpid
Date: Wed, 7 Aug 2019 07:01:20 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFEF44@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <95BCD24840F32441BEA74E0F8A31839E058F582E@SHSMSX106.ccr.corp.intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yao, BingX Y
> Sent: Monday, July 22, 2019 3:57 PM
> To: Zhu, WenhuiX <wenhuix.zhu@intel.com>; dts@dpdk.org
> Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
> Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:add not support nic on
> vlan_qinq_tpid
>
> Tested-by: Yao, BingX Y <bingx.y.yao@intel.com>
>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhuwenhui
> Sent: Monday, July 22, 2019 4:00 PM
> To: dts@dpdk.org
> Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
> Subject: [dts] [PATCH V1] conf/test_case_checklist:add not support nic on
> vlan_qinq_tpid
>
> Add fortpark_TLV nic does not support vlan_qinq_tpid.
>
> Signed-off-by: zhuwenhui <wenhuix.zhu@intel.com>
> ---
> conf/test_case_checklist.json | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index bd7db60..29b30b0 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2106,7 +2106,8 @@
> "cavium_a034",
> "cavium_a011",
> "cavium_a063",
> - "fortville_25g"
> + "fortville_25g",
> + "fortpark_TLV"
> ],
> "Target": [
> "ALL"
> --
> 2.17.2
prev parent reply other threads:[~2019-08-07 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 7:59 zhuwenhui
2019-07-22 7:56 ` Yao, BingX Y
2019-08-07 7:01 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFEF44@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=bingx.y.yao@intel.com \
--cc=dts@dpdk.org \
--cc=wenhuix.zhu@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).