From: "Ling, WeiX" <weix.ling@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 0/6] update test plan to sync with testcase
Date: Mon, 7 Sep 2020 05:52:41 +0000 [thread overview]
Message-ID: <1e1cb7fb20194e1abe73814968b5a055@intel.com> (raw)
In-Reply-To: <BN8PR11MB3715263F565B4D9EC045EE4A9E280@BN8PR11MB3715.namprd11.prod.outlook.com>
Hi lihong,
I'm sorry about it. I will update the patchset later. Please don't merge it.
Regards,
Ling Wei
-----Original Message-----
From: Ma, LihongX <lihongx.ma@intel.com>
Sent: Monday, September 7, 2020 01:19 PM
To: Ling, WeiX <weix.ling@intel.com>; dts@dpdk.org
Cc: Ling, WeiX <weix.ling@intel.com>
Subject: RE: [dts] [PATCH V1 0/6] update test plan to sync with testcase
Hi, lingwei
I think the modify of tests/TestSuite_vmdq_dcb should not be included in the series patchset.
It should meson build reference.
Regards,
Ma,lihong
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of lingwei
> Sent: Wednesday, September 2, 2020 10:15 PM
> To: dts@dpdk.org
> Cc: Ling, WeiX <weix.ling@intel.com>
> Subject: [dts] [PATCH V1 0/6] update test plan to sync with testcase
>
> update test plan to sync with testcase
>
> lingwei (6):
> tests/TestSuite_vmdq_dcb: set dpdk config before build by meson and
> use api to get app name
> test_plans/nic_single_core_perf_test_plan: update test plan to sync
> with testcase
> test_plans/pmd_test_plan: update test plan to sync with testcase
> test_plans/vmdq_test_plan: update test plan to sync with testcase
> test_plans/ptpclient_test_plan: update test plan to sync with testcase
> test_plans/vf_l3fwd_test_plan: update test plan to sync with testcase
>
> test_plans/nic_single_core_perf_test_plan.rst | 7 +++++++
> test_plans/pmd_test_plan.rst | 7 +++++++
> test_plans/ptpclient_test_plan.rst | 3 +++
> test_plans/vf_l3fwd_test_plan.rst | 9 +++++++++
> test_plans/vmdq_test_plan.rst | 5 ++++-
> tests/TestSuite_vmdq_dcb.py | 4 +++-
> 6 files changed, 33 insertions(+), 2 deletions(-)
>
> --
> 2.17.1
prev parent reply other threads:[~2020-09-07 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 14:14 lingwei
2020-09-02 14:14 ` [dts] [dts 1/6] tests/TestSuite_vmdq_dcb: set dpdk config before build by meson and use api to get app name lingwei
2020-09-02 14:14 ` [dts] [dts 2/6] test_plans/nic_single_core_perf_test_plan: update test plan to sync with testcase lingwei
2020-09-02 14:14 ` [dts] [dts 3/6] test_plans/pmd_test_plan: " lingwei
2020-09-02 14:14 ` [dts] [dts 4/6] test_plans/vmdq_test_plan: " lingwei
2020-09-02 14:14 ` [dts] [dts 5/6] test_plans/ptpclient_test_plan: " lingwei
2020-09-02 14:15 ` [dts] [dts 6/6] test_plans/vf_l3fwd_test_plan: " lingwei
2020-09-07 5:19 ` [dts] [PATCH V1 0/6] " Ma, LihongX
2020-09-07 5:52 ` Ling, WeiX [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=1e1cb7fb20194e1abe73814968b5a055@intel.com \
--to=weix.ling@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@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).