From: "Liu, Yong" <yong.liu@intel.com>
To: "Xu, HuilongX" <huilongx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Fu, JingguoX" <jingguox.fu@intel.com>
Subject: Re: [dts] [dts 1/3] [PATCH V1] add queue start/stop test for forvtille
Date: Mon, 1 Jun 2015 09:21:57 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10E36820@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1432888786-25354-1-git-send-email-huilongx.xu@intel.com>
Thanks, applied in 1.1 branch.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of huilong,xu
> Sent: Friday, May 29, 2015 4:40 PM
> To: dts@dpdk.org
> Cc: Fu, JingguoX
> Subject: [dts] [dts 1/3] [PATCH V1] add queue start/stop test for
> forvtille
>
> From: huilong xu <huilongx.xu@intel.com>
>
>
> Signed-off-by: huilong xu <huilongx.xu@intel.com>
> ---
> executions/execution_FVL.cfg | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/executions/execution_FVL.cfg b/executions/execution_FVL.cfg
> index bd278ba..f2a3e7e 100644
> --- a/executions/execution_FVL.cfg
> +++ b/executions/execution_FVL.cfg
> @@ -7,7 +7,8 @@ test_suites=
> generic_filter,
> dual_vlan,
> vlan,
> - shutdown_api
> + shutdown_api,
> + queue_start_stop
> targets=
> x86_64-native-linuxapp-gcc
> parameters=nic_type=cfg:func=true
> --
> 1.7.4.4
next prev parent reply other threads:[~2015-06-01 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 8:39 huilong,xu
2015-05-29 8:39 ` [dts] [dts 2/3] [PATCH V1] add queue start stop test plan huilong,xu
2015-06-08 1:55 ` Fu, JingguoX
2015-05-29 8:39 ` [dts] [dts 3/3] [PATCH V1] add queue start queue test code huilong,xu
2015-06-08 1:55 ` Fu, JingguoX
2015-06-01 9:21 ` Liu, Yong [this message]
2015-06-08 1:54 ` [dts] [dts 1/3] [PATCH V1] add queue start/stop test for forvtille Fu, JingguoX
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=86228AFD5BCD8E4EBFD2B90117B5E81E10E36820@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=huilongx.xu@intel.com \
--cc=jingguox.fu@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).