From: "Liu, Yong" <yong.liu@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Han, YingyaX" <yingyax.han@intel.com>
Subject: Re: [dts] [PATCH V1] add 'fortville_25g' nic test
Date: Thu, 25 Jan 2018 01:31:36 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F5A038@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1516789647-27363-1-git-send-email-yingyax.han@intel.com>
Hi Yingya,
Please make sure the content is align.
"fortville_spirit_single",
"fortville_25g"
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of han,yingya
> Sent: Wednesday, January 24, 2018 6:27 PM
> To: dts@dpdk.org
> Cc: Han, YingyaX <yingyax.han@intel.com>
> Subject: [dts] [PATCH V1] add 'fortville_25g' nic test
>
> test 'uni_pkt' on 'fortville_25g'nic
>
> Signed-off-by: han,yingya <yingyax.han@intel.com>
> ---
> conf/test_case_supportlist.json | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/conf/test_case_supportlist.json
> b/conf/test_case_supportlist.json
> index 3231733..45151f8 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -131,7 +131,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -147,7 +148,8 @@
> ],
> "NIC": [
> "powerville",
> - "niantic"
> + "niantic",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -164,7 +166,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -181,7 +184,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -198,7 +202,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -215,7 +220,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> @@ -232,7 +238,8 @@
> "NIC": [
> "fortville_eagle",
> "fortville_spirit",
> - "fortville_spirit_single"
> + "fortville_spirit_single",
> + "fortville_25g"
> ],
> "Target": [
> "ALL"
> --
> 1.9.3
prev parent reply other threads:[~2018-01-25 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 10:27 han,yingya
2018-01-25 1:31 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62F5A038@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=yingyax.han@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).