From: "Etelson, Gregory" <getelson@nvidia.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Etelson, Gregory" <getelson@nvidia.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
"Luca Vizzarro" <Luca.Vizzarro@arm.com>,
"Yoan Picchi" <yoan.picchi@foss.arm.com>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"Patrick Robb" <probb@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
"Asaf Penso" <asafp@nvidia.com>,
"Maayan Kashani" <mkashani@nvidia.com>
Subject: RE: DTS testpmd and SCAPY integration
Date: Mon, 8 Jan 2024 08:10:11 +0200 (IST) [thread overview]
Message-ID: <377a847b-7be4-bda7-9020-173b2ca5bc92@nvidia.com> (raw)
In-Reply-To: <DBAPR08MB5814862CC7A1630D1F5139D7986B2@DBAPR08MB5814.eurprd08.prod.outlook.com>
Hello Honnappa,
[snip]
> Hi Gregory,
> I do not fully understand your proposal, it will be helpful to join the DTS meetings to discuss this further.
>
Agree, let's discuss the proposal details during the DTS meeting.
> YAML has wide support built around it. By using our own text format, we will have to build the parsing support etc ourselves.
>
> However, YAML is supposed to be easy to read and understand. Is it just a matter for getting used to it?
>
I selected YAML for 2 reasons:
* Plain and intuitive YAML format minimized test meta data.
By the meta data I refer to control tags and markup characters
that are not test commands.
* YAML has Python parser.
Regards,
Gregory
next prev parent reply other threads:[~2024-01-08 6:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 7:31 Etelson, Gregory
2024-01-08 1:55 ` Honnappa Nagarahalli
2024-01-08 6:10 ` Etelson, Gregory [this message]
2024-01-08 17:36 ` Honnappa Nagarahalli
2024-01-18 12:32 ` Juraj Linkeš
2024-01-19 20:01 ` Patrick Robb
2024-01-08 12:17 ` Luca Vizzarro
2024-01-08 17:35 ` Honnappa Nagarahalli
2024-01-08 12:10 ` Luca Vizzarro
2024-01-08 17:23 ` Etelson, Gregory
2024-01-22 17:31 ` Thomas Monjalon
2024-01-23 3:42 ` Honnappa Nagarahalli
2024-01-23 8:50 ` Thomas Monjalon
2024-01-23 18:26 ` Jeremy Spewock
2024-01-28 13:44 ` Gregory Etelson
2024-01-30 22:03 ` Patrick Robb
2024-01-31 7:42 ` Etelson, Gregory
2024-02-14 17:27 ` Gregory Etelson
2024-02-19 5:08 ` Patrick Robb
2024-02-20 13:35 ` Gregory Etelson
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=377a847b-7be4-bda7-9020-173b2ca5bc92@nvidia.com \
--to=getelson@nvidia.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=asafp@nvidia.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=mkashani@nvidia.com \
--cc=nd@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--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).