test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Gu, YongjieX" <yongjiex.gu@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] remove n/a suites from execution_FVL.cfg
Date: Thu, 22 Oct 2015 07:55:52 +0000	[thread overview]
Message-ID: <E1E7EC9273ACA248A8E9BE46A66CE0A03C4B2FFA@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5628939C.9020007@intel.com>

Ok,I will keep it ,and send another patch later.
thanks

-----Original Message-----
From: Liu, Yong 
Sent: Thursday, October 22, 2015 3:43 PM
To: Gu, YongjieX; dts@dpdk.org
Subject: Re: [dts] [PATCH] remove n/a suites from execution_FVL.cfg

Hi Yongjie,
I remember vxlan_sample should also be one of FVL supported feature. Why remove  this case?

On 10/21/2015 10:12 AM, guyongjie wrote:
> From: Gu yongjie <yongjiex.gu@intel.com>
>
>
> Signed-off-by: Gu yongjie <yongjiex.gu@intel.com>
> ---
>   executions/execution_FVL.cfg |    6 ++++--
>   1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/executions/execution_FVL.cfg 
> b/executions/execution_FVL.cfg index 7bdd2b7..0d55d21 100644
> --- a/executions/execution_FVL.cfg
> +++ b/executions/execution_FVL.cfg
> @@ -13,19 +13,21 @@ test_suites=
>       fdir,
>       nvgre,
>       vxlan,
> -    vxlan_sample,
>       pmd,
>       ipfrag,
>       timer,
>       jumboframes,
>       multiprocess,
> -    l2fwd,
>       whitelist,
>       blacklist,
>       ipv4_reassembly,
>       scatter,
>       pmdrssreta,
>       pmdrss_hash,
> +    ipv6_reassembly,
> +    link_status_interrupt,
> +    pmd_pcap,
> +    interrupt_pmd,
>       ieee1588,
>       kni
>   targets=

      reply	other threads:[~2015-10-22  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  2:12 [dts] [PATCH] remove n/a suites from execution.cfg guyongjie
2015-10-21  2:12 ` [dts] [PATCH] remove n/a suites from execution_FVL.cfg guyongjie
2015-10-22  7:43   ` Liu, Yong
2015-10-22  7:55     ` Gu, YongjieX [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=E1E7EC9273ACA248A8E9BE46A66CE0A03C4B2FFA@SHSMSX101.ccr.corp.intel.com \
    --to=yongjiex.gu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yong.liu@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).