test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "apvukkisala@marvell.com" <apvukkisala@marvell.com>
Subject: Re: [dts] [PATCH] test_case_checklist.json: Added checklist for the	test cases which doesn't supported by cavium_a064
Date: Fri, 20 Dec 2019 07:53:21 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB8A140@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1576226850-18909-1-git-send-email-nareddy@marvell.com>

Applied failed, could you please rework the patch, thanks very much

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Friday, December 13, 2019 4:48 PM
> To: dts@dpdk.org
> Cc: apvukkisala@marvell.com; Praneeth Reddy <nareddy@marvell.com>
> Subject: [dts] [PATCH] test_case_checklist.json: Added checklist for the test
> cases which doesn't supported by cavium_a064
> 
> From: Praneeth Reddy <nareddy@marvell.com>
> 
> The following test cases are not supported by cavium_a064 link_stats
> pmd_burst pmd_continues
> 
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
>  conf/test_case_checklist.json | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
> index 38b1335..d0d066f 100644
> --- a/conf/test_case_checklist.json
> +++ b/conf/test_case_checklist.json
> @@ -342,7 +342,8 @@
>                  "springville",
>                  "ironpond",
>                  "cavium_a034",
> -                "cavium_0011"
> +                "cavium_0011",
> +                "cavium_a064"
>              ],
>              "Target": [
>                  "ALL"
> @@ -1296,7 +1297,8 @@
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single",
> -                "fortville_25g"
> +                "fortville_25g",
> +                "cavium_a064"
>              ],
>              "Target": [
>                  "ALL"
> @@ -1341,7 +1343,8 @@
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single",
> -                "fortville_25g"
> +                "fortville_25g",
> +                "cavium_a064"
>              ],
>              "Target": [
>                  "ALL"
> --
> 1.8.3.1


      reply	other threads:[~2019-12-20  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13  8:47 nareddy
2019-12-20  7:53 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB8A140@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=apvukkisala@marvell.com \
    --cc=dts@dpdk.org \
    --cc=nareddy@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).