From: Jun Dong <junx.dong@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, qingx.sun@intel.com, junx.dong@intel.com
Subject: [dts] [V2 2/4] doc/dts_gsg: removed makefile from user guide document
Date: Fri, 25 Feb 2022 13:43:35 +0800 [thread overview]
Message-ID: <20220225054337.3668-3-junx.dong@intel.com> (raw)
In-Reply-To: <20220225054337.3668-1-junx.dong@intel.com>
Makefile builds have been deprecated, so:
- remove makefile relation description from user guide document.
Signed-off-by: Jun Dong <junx.dong@intel.com>
---
doc/dts_gsg/usr_guide/usage.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/dts_gsg/usr_guide/usage.rst b/doc/dts_gsg/usr_guide/usage.rst
index 391662f6..ba714703 100644
--- a/doc/dts_gsg/usr_guide/usage.rst
+++ b/doc/dts_gsg/usr_guide/usage.rst
@@ -24,7 +24,7 @@ First of all, you must configure execution.cfg as below:
* crbs: IP address of the DUT. The detail information is defined in file $DTS_CFG_FOLDER/crbs.cfg.
* drivername: the driver devices used by DPDK bound to.
-* build_type: the tool for building DPDK, it can be meson and makefile. DPDK 20.11+ only uses meson and ninja.
+* build_type: the tool for building DPDK, it can be meson.
* rx_mode: vector instructions used in tests, it can be novector/sse/avx2/avx512. it is optional, if not set, dpdk uses avx2 by default.
* test_suites: test suites and cases that to be executed. use ``:`` to separate suite and it's cases and use ``\`` to separate different cases.
* targets: DPDK targets to be tested.
--
2.33.1.windows.1
next prev parent reply other threads:[~2022-02-25 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 5:43 [dts] [V2 0/4] removed makefile relation content Jun Dong
2022-02-25 5:43 ` [dts] [V2 1/4] executions/execution*: removed makefile from configure Jun Dong
2022-02-25 5:43 ` Jun Dong [this message]
2022-02-25 5:43 ` [dts] [V2 3/4] framework/*: removed makefile from framework Jun Dong
2022-02-25 5:43 ` [dts] [V2 4/4] tests/*: removed makefile from test suite Jun Dong
2022-02-27 14:27 ` Tu, Lijuan
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=20220225054337.3668-3-junx.dong@intel.com \
--to=junx.dong@intel.com \
--cc=dts@dpdk.org \
--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).