From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dts] [PATCH V1 2/2] tests/dcf_lifecycle: add test plan index
Date: Fri, 19 Jun 2020 08:17:29 +0000 [thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41FEE2E7@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20200617024325.23247-3-yufengx.mo@intel.com>
Acked-by: Chen, Zhaoyan <zhaoyan.chen@intel.com>
Regards,
Zhaoyan Chen
> -----Original Message-----
> From: Mo, YufengX <yufengx.mo@intel.com>
> Sent: Wednesday, June 17, 2020 10:43 AM
> To: dts@dpdk.org; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V1 2/2] tests/dcf_lifecycle: add test plan index
>
>
> add test plan index.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> test_plans/index.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/test_plans/index.rst b/test_plans/index.rst index
> 6f5724b..2491e16 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -45,6 +45,7 @@ The following are the test plans for the DPDK DTS
> automated test system.
> cvl_advanced_rss_test_plan
> cvl_fdir_test_plan
> cvl_switch_filter_test_plan
> + dcf_lifecycle_test_plan
> crypto_perf_cryptodev_perf_test_plan
> ddp_gtp_qregion_test_plan
> ddp_gtp_test_plan
> --
> 2.21.0
prev parent reply other threads:[~2020-06-19 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 2:43 [dts] [PATCH V1 0/2] test_plans/dcf_lifecycle: update test plan yufengmx
2020-06-17 2:43 ` [dts] [PATCH V1 1/2] tests/dcf_lifecycle: " yufengmx
2020-06-19 6:20 ` Tu, Lijuan
2020-06-19 8:17 ` Chen, Zhaoyan
2020-06-17 2:43 ` [dts] [PATCH V1 2/2] tests/dcf_lifecycle: add test plan index yufengmx
2020-06-19 8:17 ` Chen, Zhaoyan [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=9DEEADBC57E43F4DA73B571777FECECA41FEE2E7@SHSMSX104.ccr.corp.intel.com \
--to=zhaoyan.chen@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).