From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Jun Dong <junx.dong@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "lijuan.tu@intel.com" <lijuan.tu@intel.com>,
"qingx.sun@intel.com" <qingx.sun@intel.com>
Subject: RE: [V3 1/5] rename base classes 1
Date: Fri, 10 Jun 2022 12:41:14 +0000 [thread overview]
Message-ID: <4487d706463844fcb6cf355a609c811b@pantheon.tech> (raw)
In-Reply-To: <20220610050810.1531-2-junx.dong@intel.com>
Reviewed-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> -----Original Message-----
> From: Jun Dong <junx.dong@intel.com>
> Sent: Friday, June 10, 2022 7:08 AM
> To: dts@dpdk.org
> Cc: lijuan.tu@intel.com; qingx.sun@intel.com; junx.dong@intel.com; Juraj
> Linkeš <juraj.linkes@pantheon.tech>
> Subject: [V3 1/5] rename base classes 1
>
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
>
> conf/*
> doc/*
> execution/*
> execution.cfg
> removed output/
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Signed-off-by: Jun Dong <junx.dong@intel.com>
> ---
> conf/crbs.cfg | 42 -----
> conf/l3fwd.cfg | 2 +-
> conf/performance_thread.cfg | 2 +-
> conf/ports.cfg | 18 +--
> conf/power_bidirection_channel.cfg | 2 +-
> conf/power_branch_ratio.cfg | 2 +-
> conf/power_negative.cfg | 2 +-
> conf/scene/dpdk_vf_passthrough.cfg | 16 +-
> conf/scene/pf_passthrough.cfg | 14 +-
> conf/scene/vf_passthrough.cfg | 14 +-
> conf/scene/vf_passthrough_1.cfg | 14 +-
> conf/testpmd_perf.cfg | 2 +-
> conf/topology.cfg | 42 +++++
> conf/{pktgen.cfg => traffic_generator.cfg} | 24 +--
> conf/vhost_peer_conf.cfg | 2 +-
> conf/vm_power_manager.cfg | 2 +-
> conf/vm_pw_mgmt_policy.cfg | 2 +-
> doc/dts_gsg/image/virt_flow.svg | 28 ++--
> doc/dts_gsg/quick_start.rst | 122 ++++++++-------
> doc/dts_gsg/usr_guide/igb_uio.rst | 2 +-
> doc/dts_gsg/usr_guide/index.rst | 2 +-
> doc/dts_gsg/usr_guide/intro.rst | 18 ++-
> doc/dts_gsg/usr_guide/ixia.rst | 144 +++++++++---------
> doc/dts_gsg/usr_guide/results.rst | 12 +-
> .../{setup_dut.rst => setup_sut.rst} | 8 +-
> doc/dts_gsg/usr_guide/sys_reqs.rst | 18 +--
> doc/dts_gsg/usr_guide/trex.rst | 104 ++++++-------
> doc/dts_gsg/usr_guide/usage.rst | 110 ++++++-------
> execution.cfg | 2 +-
> executions/execution.cfg | 4 +-
> executions/execution_FVL.cfg | 4 +-
> executions/execution_fm10k.cfg | 4 +-
> executions/execution_rxmode.cfg | 6 +-
> executions/execution_smoke.cfg | 2 +-
> output/Readme.txt | 2 -
> 35 files changed, 403 insertions(+), 391 deletions(-)
> delete mode 100644 conf/crbs.cfg
> create mode 100644 conf/topology.cfg
> rename conf/{pktgen.cfg => traffic_generator.cfg} (81%)
> rename doc/dts_gsg/usr_guide/{setup_dut.rst => setup_sut.rst} (97%)
> delete mode 100644 output/Readme.txt
>
next prev parent reply other threads:[~2022-06-10 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 5:08 [V3 0/5] rename base classes Jun Dong
2022-06-10 5:08 ` [V3 1/5] rename base classes 1 Jun Dong
2022-06-10 12:41 ` Juraj Linkeš [this message]
2022-06-10 5:08 ` [V3 2/5] rename base classes 2 Jun Dong
2022-06-10 12:41 ` Juraj Linkeš
2022-06-10 5:08 ` [V3 3/5] rename base classes 3 Jun Dong
2022-06-10 12:41 ` Juraj Linkeš
2022-06-10 5:08 ` [V3 4/5] rename base classes 4 Jun Dong
2022-06-10 12:42 ` Juraj Linkeš
2022-06-10 5:08 ` [V3 5/5] rename base classes 5 Jun Dong
2022-06-10 12:43 ` Juraj Linkeš
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=4487d706463844fcb6cf355a609c811b@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dts@dpdk.org \
--cc=junx.dong@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qingx.sun@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).