From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] conf/checklist:add not support case on FVL.
Date: Tue, 15 Jan 2019 06:00:25 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA029BB@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1547185342-25148-1-git-send-email-shuaix.zhu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
> Sent: Friday, January 11, 2019 1:42 PM
> To: dts@dpdk.org
> Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
> Subject: [dts] [PATCH V1] conf/checklist:add not support case on FVL.
>
> The following case is skipped:
> port_mtu,
> retrieve_reg
>
> Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
> ---
> conf/test_case_checklist.json | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index
> b4e7126..fec4c5a 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -1911,7 +1911,13 @@
> "ALL"
> ],
> "NIC": [
> - "ALL"
> + "fortville_eagle",
> + "fortville_spirit",
> + "fortville_spirit_single",
> + "fortville_25g",
> + "fortpark",
> + "fortpark_TLV",
> + "fortpark_TLV_vf"
> ],
> "Target": [
> "ALL"
> @@ -2149,5 +2155,26 @@
> "Bug ID": "",
> "Comments": "the nic not support this case"
> }
> + ],
> + "retrieve_reg": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "fortville_eagle",
> + "fortville_spirit",
> + "fortville_spirit_single",
> + "fortville_25g",
> + "fortpark",
> + "fortpark_TLV",
> + "fortpark_TLV_vf"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "the nic not support this case"
> + }
> ]
> }
> --
> 2.17.2
prev parent reply other threads:[~2019-01-15 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 5:42 zhu,shuai
2019-01-11 10:06 ` Wu, ChangqingX
2019-01-15 6:00 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA029BB@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.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).