From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1 00/14] test_plans: fix build warnings and errors
Date: Sun, 28 Jun 2020 06:44:10 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC65977@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1592878901-216102-1-git-send-email-haiyangx.zhao@intel.com>
Applied the series except " test_plans/cvl_advanced_iavf_rss: fix build warnings and errors " because applied error, thanks
-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of Haiyang Zhao
Sent: 2020年6月23日 10:21
To: dts@dpdk.org
Cc: Zhao, HaiyangX <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1 00/14] test_plans: fix build warnings and errors
*.fix test plans build warnings and errors
Haiyang Zhao (14):
test_plans/cvl_advanced_iavf_rss: fix build warnings and errors
test_plans/cvl_fdir: fix build warnings and errors
test_plans/fortville_rss_input: fix build warnings and errors
test_plans/generic_flow_api: fix build warnings and errors
test_plans/iavf_fdir: fix build warnings and errors
test_plans/iavf_package_driver_error_handle: fix build warnings and
errors
test_plans/l2tp_esp_coverage: fix build warnings and errors
test_plans/loopback_virtio_user_server_mode: fix build warnings and
errors
test_plans/pvp_multi_paths_performance: fix build warnings and errors
test_plans/pvp_multi_paths_virtio_single_core_performance: fix build
warnings and errors
test_plans/rss_to_rte_flow: fix build warnings and errors
test_plans/stats_checks: fix build warnings and errors
test_plans/vm2vm_virtio_net_perf: fix build warnings and errors
test_plans/index: fix build warnings and errors *.add new added
test plans *.fix typo error.
test_plans/cvl_advanced_iavf_rss_test_plan.rst | 331 +++++++++++++++------
test_plans/cvl_fdir_test_plan.rst | 2 +-
test_plans/fortville_rss_input_test_plan.rst | 6 +-
test_plans/generic_flow_api_test_plan.rst | 2 +
test_plans/iavf_fdir_test_plan.rst | 6 +-
.../iavf_package_driver_error_handle_test_plan.rst | 4 +-
test_plans/index.rst | 11 +-
test_plans/l2tp_esp_coverage_test_plan.rst | 70 ++---
.../loopback_virtio_user_server_mode_test_plan.rst | 68 ++---
.../pvp_multi_paths_performance_test_plan.rst | 2 +
...hs_virtio_single_core_performance_test_plan.rst | 2 +-
test_plans/rss_to_rte_flow_test_plan.rst | 4 +-
test_plans/stats_checks_test_plan.rst | 2 +-
test_plans/vm2vm_virtio_net_perf_test_plan.rst | 2 +-
14 files changed, 335 insertions(+), 177 deletions(-)
--
1.8.3.1
prev parent reply other threads:[~2020-06-28 6:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 2:21 Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 01/14] test_plans/cvl_advanced_iavf_rss: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 02/14] test_plans/cvl_fdir: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 03/14] test_plans/fortville_rss_input: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 04/14] test_plans/generic_flow_api: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 05/14] test_plans/iavf_fdir: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 06/14] test_plans/iavf_package_driver_error_handle: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 07/14] test_plans/l2tp_esp_coverage: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 08/14] test_plans/loopback_virtio_user_server_mode: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 09/14] test_plans/pvp_multi_paths_performance: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 10/14] test_plans/pvp_multi_paths_virtio_single_core_performance: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 11/14] test_plans/rss_to_rte_flow: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 12/14] test_plans/stats_checks: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 13/14] test_plans/vm2vm_virtio_net_perf: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 14/14] test_plans/index: " Haiyang Zhao
2020-06-28 6:44 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BC65977@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=haiyangx.zhao@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).