From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "thaq@marvell.com" <thaq@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH] conf/test_case_checklist.json: Listing ethtool retrieve_reg test case as Invaild for cavium_0a63 card.
Date: Wed, 3 Jul 2019 05:56:59 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAD92FC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1561960325-12132-1-git-send-email-thaq@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com
> Sent: Monday, July 1, 2019 1:52 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; Thanseerulhaq
> <thaq@marvell.com>
> Subject: [dts] [PATCH] conf/test_case_checklist.json: Listing ethtool
> retrieve_reg test case as Invaild for cavium_0a63 card.
>
> From: Thanseerulhaq <thaq@marvell.com>
>
> Moviing to it correct retrieve_reg test block
>
> Signed-off-by: Thanseerulhaq <thaq@marvell.com>
> ---
> conf/test_case_checklist.json | 16 +---------------
> 1 file changed, 1 insertion(+), 15 deletions(-)
>
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 610bef1..49bda03 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -2196,6 +2196,7 @@
> "fortville_25g",
> "fortpark",
> "fortpark_TLV",
> + "cavium_a063",
> "fortpark_TLV_vf"
> ],
> "Target": [
> @@ -2285,21 +2286,6 @@
> "Comments": "the nic not support this case"
> }
> ],
> - "retrieve_reg": [
> - {
> - "OS": [
> - "ALL"
> - ],
> - "NIC": [
> - "cavium_a063"
> - ],
> - "Target": [
> - "ALL"
> - ],
> - "Bug ID": "",
> - "Comments": "the nic not support this case"
> - }
> - ],
> "vlan_change_tpid": [
> {
> "OS": [
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-07-03 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 5:52 thaq
2019-07-03 5:56 ` Tu, Lijuan [this message]
2019-07-03 6:00 ` Tu, Lijuan
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=8CE3E05A3F976642AAB0F4675D0AD20E0BAD92FC@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=thaq@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).