test suite reviews and discussions
 help / color / mirror / Atom feed
From: Manindra Tammineedi <manindrat@biarca.com>
To: bingx.y.yao@intel.com
Cc: dts@dpdk.org
Subject: Re: [dts] [PATCH V1] tests/vlan_ethertype_config:hardware only supports fortville NIC
Date: Thu, 25 Oct 2018 11:37:19 +0530	[thread overview]
Message-ID: <CALoo5yAFE7yNeCT3ha8ORj0hQ44B24ifGFSJTpM=HAoy_4A5QQ@mail.gmail.com> (raw)
In-Reply-To: <1540446878-12493-1-git-send-email-bingx.y.yao@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Sure, Will check that. Appropriate your help

Thanks & Regards,
Manindra

On Thu, Oct 25, 2018 at 11:21 AM yaobing <bingx.y.yao@intel.com> wrote:

> check rst script find that hardware only supports Fortville NIC (4x 10G or
> 2x10G or 2x40G or 1x10G)
>
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
>  conf/test_case_supportlist.json | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/conf/test_case_supportlist.json
> b/conf/test_case_supportlist.json
> index f97b90d..8e76521 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -540,5 +540,21 @@
>              "Bug ID": "",
>              "Comments": "This case only support i40e driver nic"
>          }
> +    ],
> +    "vlan_qinq_tpid": [
> +        {
> +            "OS": [
> +                "ALL"
> +            ],
> +            "NIC": [
> +                "fortville_eagle",
> +                "fortville_spirit"
> +            ],
> +            "Target": [
> +                "ALL"
> +            ],
> +            "Bug ID": "",
> +            "Comments": "This case only support fortville nic(4x 10G or
> 2x10G or 2x40G or 1x10G)"
> +        }
>      ]
>  }
> --
> 2.17.2
>
>

[-- Attachment #2: Type: text/html, Size: 1941 bytes --]

  reply	other threads:[~2018-10-25  6:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  5:54 yaobing
2018-10-25  6:07 ` Manindra Tammineedi [this message]
2018-10-25  9:10 ` 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='CALoo5yAFE7yNeCT3ha8ORj0hQ44B24ifGFSJTpM=HAoy_4A5QQ@mail.gmail.com' \
    --to=manindrat@biarca.com \
    --cc=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    /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).