From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V1 0/7] meson build reference
Date: Mon, 20 Jul 2020 07:08:05 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC82257@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1594089903-26285-1-git-send-email-lihongx.ma@intel.com>
Applied the series, thanks
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of lihong
> Sent: 2020年7月7日 10:45
> To: dts@dpdk.org
> Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>; Ma, LihongX
> <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1 0/7] meson build reference
>
>
> lihong (7):
> executions: add build_type field in all executions cfg
> conf: add configuration file of app_name.cfg
> framework/config: get configuration information from app_name.cfg
> framework: read and save the build_type from execution.cfg
> framework: add meson build method and get apps name of current build
> type
> framework/pmd_output: replace the hard code app path with the
> configured app path
> tests: replace the hard code app path with the configured app path
>
> conf/app_name.cfg | 119 +++++++++++++++++++++++++++
> executions/execution.cfg | 2 +
> executions/execution_FVL.cfg | 2 +
> executions/execution_fm10k.cfg | 2 +
> executions/execution_rxmode.cfg | 3 +
> executions/execution_smoke.cfg | 1 +
> framework/config.py | 29 +++++++
> framework/dts.py | 7 ++
> framework/dut.py | 8 +-
> framework/pmd_output.py | 3 +-
> framework/project_dpdk.py | 128 ++++++++++++++++++++++++++++--
> framework/settings.py | 1 +
> tests/TestSuite_multiprocess.py | 53 ++++++++-----
> tests/TestSuite_vhost_multi_queue_qemu.py | 14 ++--
> 14 files changed, 335 insertions(+), 37 deletions(-) create mode 100644
> conf/app_name.cfg
>
> --
> 2.7.4
prev parent reply other threads:[~2020-07-20 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:44 lihong
2020-07-07 2:44 ` [dts] [PATCH V1 1/7] executions: add build_type field in all executions cfg lihong
2020-07-07 2:44 ` [dts] [PATCH V1 2/7] conf: add configuration file of app_name.cfg lihong
2020-07-07 2:44 ` [dts] [PATCH V1 3/7] framework/config: get configuration information from app_name.cfg lihong
2020-07-07 2:45 ` [dts] [PATCH V1 4/7] framework: read and save the build_type from execution.cfg lihong
2020-07-07 2:45 ` [dts] [PATCH V1 5/7] framework: add meson build method and get apps name of current build type lihong
2020-07-07 2:45 ` [dts] [PATCH V1 6/7] framework/pmd_output: replace the hard code app path with the configured app path lihong
2020-07-07 2:45 ` [dts] [PATCH V1 7/7] tests: " lihong
2020-07-07 10:20 ` [dts] [PATCH V1 0/7] meson build reference Xiao, QimaiX
2020-07-20 7:08 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC82257@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=zhaoyan.chen@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).