DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
	Honnappa.Nagarahalli@arm.com, ohilyard@iol.unh.edu,
	lijuan.tu@intel.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [RFC PATCH v1 12/13] dts: merge DTS executions/execution_smoke.cfg to DPDK
Date: Wed,  6 Apr 2022 15:07:41 +0000	[thread overview]
Message-ID: <20220406150742.2914878-13-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <20220406150742.2914878-1-juraj.linkes@pantheon.tech>

---
 dts/executions/execution_smoke.cfg | 32 ++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 dts/executions/execution_smoke.cfg

diff --git a/dts/executions/execution_smoke.cfg b/dts/executions/execution_smoke.cfg
new file mode 100644
index 0000000000..6f35578db0
--- /dev/null
+++ b/dts/executions/execution_smoke.cfg
@@ -0,0 +1,32 @@
+[Execution1]
+crbs=<CRB IP Address>
+#using igb_uio please refer to doc/dts_gsg/support_igb_uio.rst
+drivername=<driver name igb_uio or vfio-pci or mlx5_core or uio_pci_generic>
+build_type=<meson>
+test_suites=
+    unit_tests_cmdline,
+    unit_tests_eal,
+    unit_tests_dump,
+    unit_tests_kni,
+    unit_tests_lpm,
+    unit_tests_mbuf,
+    unit_tests_mempool,
+    unit_tests_power,
+    unit_tests_pmd_perf,
+    unit_tests_qos,
+    unit_tests_ring,
+    unit_tests_ringpmd,
+    unit_tests_timer,
+    dynamic_config,
+    jumboframes,
+    scatter,
+    ieee1588,
+    multiprocess,
+    l2fwd,
+    pmd,
+    checksum_offload,
+    mac_filter,
+    blocklist
+targets=
+    x86_64-native-linuxapp-gcc
+parameters=nic_type=niantic:func=true
-- 
2.20.1


  parent reply	other threads:[~2022-04-06 15:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:07 [RFC PATCH v1 00/13] merge DTS conf files " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 01/13] dts: merge DTS conf/crbs.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 02/13] dts: merge DTS conf/pktgen.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 03/13] dts: merge DTS conf/ports.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 04/13] dts: merge DTS conf/suite_sample.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 05/13] dts: merge DTS conf/test_case_checklist.json " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 06/13] dts: merge DTS conf/test_case_supportlist.json " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 07/13] dts: merge DTS execution.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 08/13] dts: merge DTS executions/execution.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 09/13] dts: merge DTS executions/execution_FVL.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 10/13] dts: merge DTS executions/execution_fm10k.cfg " Juraj Linkeš
2022-04-06 15:07 ` [RFC PATCH v1 11/13] dts: merge DTS executions/execution_rxmode.cfg " Juraj Linkeš
2022-04-06 15:07 ` Juraj Linkeš [this message]
2022-04-06 15:07 ` [RFC PATCH v1 13/13] dts: merge DTS framework/settings.py " 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=20220406150742.2914878-13-juraj.linkes@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).