From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "pvukkisala@marvell.com" <pvukkisala@marvell.com>
Subject: Re: [dts] [PATCH] test_case_checklist.json: Added not supported list for cavium_a063 and cavium_a064
Date: Fri, 27 Dec 2019 06:12:01 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB8ECB1@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1577082349-26936-1-git-send-email-nareddy@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Monday, December 23, 2019 2:26 PM
> To: dts@dpdk.org
> Cc: pvukkisala@marvell.com; Praneeth Reddy <nareddy@marvell.com>
> Subject: [dts] [PATCH] test_case_checklist.json: Added not supported list for
> cavium_a063 and cavium_a064
>
> From: Praneeth Reddy <nareddy@marvell.com>
>
> The following test cases are not supported for cavium_a064
> - retrieve_eeprom
>
> The following test cases are not supported for cavium_a064
> - pmd_continues
> - pmd_burst
> - link_stats
>
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
> conf/test_case_checklist.json | 25 ++++++++++++++++++++++---
> 1 file changed, 22 insertions(+), 3 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 72d53e7..82eb404 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -346,7 +346,8 @@
> "springville",
> "ironpond",
> "cavium_a034",
> - "cavium_0011"
> + "cavium_0011",
> + "cavium_a064"
> ],
> "Target": [
> "ALL"
> @@ -1304,7 +1305,8 @@
> "fortville_eagle",
> "fortville_spirit",
> "fortville_spirit_single",
> - "fortville_25g"
> + "fortville_25g",
> + "cavium_a064"
> ],
> "Target": [
> "ALL"
> @@ -1349,7 +1351,8 @@
> "fortville_eagle",
> "fortville_spirit",
> "fortville_spirit_single",
> - "fortville_25g"
> + "fortville_25g",
> + "cavium_a064"
> ],
> "Target": [
> "ALL"
> @@ -2441,5 +2444,21 @@
> "Bug ID": "",
> "Comments": "the nic not support this case"
> }
> + ],
> + "retrieve_eeprom": [
> + {
> + "OS": [
> + "ALL"
> + ],
> + "NIC": [
> + "cavium_a063",
> + "cavium_a064"
> + ],
> + "Target": [
> + "ALL"
> + ],
> + "Bug ID": "",
> + "Comments": "the nic not support this case"
> + }
> ]
> }
> --
> 1.8.3.1
prev parent reply other threads:[~2019-12-27 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 6:25 nareddy
2019-12-27 6:12 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB8ECB1@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=nareddy@marvell.com \
--cc=pvukkisala@marvell.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).