From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>
Subject: Re: [dts] [PATCH V2] conf/test_case_checklist:fix repeat conflict of retrieve_reg
Date: Tue, 25 Feb 2020 05:36:39 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBCDDE1@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1582600929-243500-1-git-send-email-xiaoxiaox.zeng@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zeng Xiaoxiao
> Sent: Tuesday, February 25, 2020 11:22 AM
> To: dts@dpdk.org
> Cc: Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
> Subject: [dts] [PATCH V2] conf/test_case_checklist:fix repeat conflict of
> retrieve_reg
>
> Signed-off-by: Zeng Xiaoxiao <xiaoxiaox.zeng@intel.com>
> ---
> conf/test_case_checklist.json | 20 +++-----------------
> 1 file changed, 3 insertions(+), 17 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 68e8dcd..d42dca6 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2257,7 +2257,9 @@
> "fortpark_TLV",
> "cavium_a063",
> "fortpark_TLV_vf",
> - "cavium_a064"
> + "cavium_a064",
> + "columbiaville_25g",
> + "columbiaville_100g"
> ],
> "Target": [
> "ALL"
> @@ -2611,22 +2613,6 @@
> "Comments": "the nic not support this case"
> }
> ],
> - "retrieve_reg": [
> - {
> - "OS": [
> - "ALL"
> - ],
> - "NIC": [
> - "columbiaville_25g",
> - "columbiaville_100g"
> - ],
> - "Target": [
> - "ALL"
> - ],
> - "Bug ID": "",
> - "Comments": "the nic not support this case"
> - }
> - ],
> "vf_vlan_rx": [
> {
> "OS": [
> --
> 1.8.3.1
prev parent reply other threads:[~2020-02-25 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 3:22 Zeng Xiaoxiao
2020-02-25 5:36 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBCDDE1@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xiaoxiaox.zeng@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).