From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V3 2/2] test_plans/index: add packet_capture_test_plan label
Date: Tue, 6 Aug 2019 10:07:52 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFD61C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1562728176-214925-3-git-send-email-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Wednesday, July 10, 2019 11:10 AM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V3 2/2] test_plans/index: add
> packet_capture_test_plan label
>
>
> add packet_capture_test_plan label
>
> 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
> 52d4e55..b49c5eb 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -217,3 +217,4 @@ The following are the test plans for the DPDK DTS
> automated test system.
> efd_test_plan
> example_build_test_plan
> flow_classify_test_plan
> + packet_capture_test_plan
> --
> 1.9.3
next prev parent reply other threads:[~2019-08-06 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 3:09 [dts] [PATCH V3 0/2] test_plans/packet_capture: upload test plan yufengmx
2019-07-10 3:09 ` [dts] [PATCH V3 1/2] " yufengmx
2019-07-10 3:19 ` Wang, Yinan
2019-08-06 10:07 ` Tu, Lijuan
2019-07-10 3:09 ` [dts] [PATCH V3 2/2] test_plans/index: add packet_capture_test_plan label yufengmx
2019-07-10 3:20 ` Wang, Yinan
2019-08-06 10:07 ` Tu, Lijuan [this message]
2019-07-10 3:20 ` [dts] [PATCH V3 0/2] test_plans/packet_capture: upload test plan Wang, Yinan
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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFD61C@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@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).