From: jspewock@iol.unh.edu
To: Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
thomas@monjalon.net, wathsala.vithanage@arm.com,
probb@iol.unh.edu, paul.szczepanek@arm.com,
yoan.picchi@foss.arm.com, ferruh.yigit@amd.com,
andrew.rybchenko@oktetlabs.ru
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v1 3/7] dts: add scatter to the yaml schema
Date: Thu, 9 Nov 2023 18:07:33 -0500 [thread overview]
Message-ID: <20231109230900.24572-4-jspewock@iol.unh.edu> (raw)
In-Reply-To: <20231109230900.24572-1-jspewock@iol.unh.edu>
From: Jeremy Spewock <jspewock@iol.unh.edu>
Allow for scatter to be specificed in the configuration file.
Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu>
---
dts/framework/config/conf_yaml_schema.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dts/framework/config/conf_yaml_schema.json b/dts/framework/config/conf_yaml_schema.json
index 84e45fe3c2..97ee32f47a 100644
--- a/dts/framework/config/conf_yaml_schema.json
+++ b/dts/framework/config/conf_yaml_schema.json
@@ -186,7 +186,8 @@
"type": "string",
"enum": [
"hello_world",
- "os_udp"
+ "os_udp",
+ "scatter"
]
},
"test_target": {
--
2.42.0
next prev parent reply other threads:[~2023-11-09 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 23:07 [PATCH v1 0/7] dts: Port scatter suite over jspewock
2023-11-09 23:07 ` [PATCH v1 1/7] dts: Add scatter test suite jspewock
2023-11-09 23:07 ` [PATCH v1 2/7] dts: add waiting for port up in testpmd jspewock
2023-11-09 23:07 ` jspewock [this message]
2023-11-09 23:07 ` [PATCH v1 4/7] dts: allow passing parameters into interactive apps jspewock
2023-11-09 23:07 ` [PATCH v1 5/7] dts: add optional packet filtering to scapy sniffer jspewock
2023-11-09 23:07 ` [PATCH v1 6/7] dts: add pci addresses to EAL parameters jspewock
2023-11-09 23:07 ` [PATCH v1 7/7] dts: allow configuring MTU of ports jspewock
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=20231109230900.24572-4-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=juraj.linkes@pantheon.tech \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=yoan.picchi@foss.arm.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).