From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhang, YanX A" <yanx.a.zhang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, YanX A" <yanx.a.zhang@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:add not support nic on two_vms_pool_down_mirrors
Date: Wed, 4 Dec 2019 05:29:08 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB7C285@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1573629004-51626-1-git-send-email-yanx.a.zhang@intel.com>
Hi yan,
Your patch need to be reworked, as code base changed.
Thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhang,yan
> Sent: Wednesday, November 13, 2019 3:10 PM
> To: dts@dpdk.org
> Cc: Zhang, YanX A <yanx.a.zhang@intel.com>
> Subject: [dts] [PATCH V1] conf/test_case_checklist:add not support nic on
> two_vms_pool_down_mirrors
>
> add not support nic on two_vms_pool_down_mirrors.
>
> Signed-off-by: zhang,yan <yanx.a.zhang@intel.com>
> ---
> conf/test_case_checklist.json | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 53c5221..4efa1fc 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2365,5 +2365,21 @@
> "Bug ID": "",
> "Comments": "the nic not support this case"
> }
> + ],
> + "two_vms_pool_down_mirrors": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "niantic",
> + "sagepond"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "Niantic not support this case"
> + }
> ]
> }
> --
> 2.17.2
prev parent reply other threads:[~2019-12-04 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 7:10 zhang,yan
2019-11-13 7:06 ` Zhang, YanX A
2019-12-04 5:29 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB7C285@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yanx.a.zhang@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).