From: Paul Szczepanek <paul.szczepanek@arm.com>
To: Nicholas Pratte <npratte@iol.unh.edu>,
luca.vizzarro@arm.com, juraj.linkes@pantheon.tech,
jspewock@iol.unh.edu, dmarx@iol.unh.edu,
yoan.picchi@foss.arm.com, Honnappa.Nagarahalli@arm.com,
probb@iol.unh.edu
Cc: nd@arm.com, dev@dpdk.org
Subject: Re: [RFC v1 1/1] dts: split enums from primary json schema
Date: Wed, 8 Jan 2025 10:05:35 +0000 [thread overview]
Message-ID: <f3f795cf-369b-4467-892b-c5279f4e6623@arm.com> (raw)
In-Reply-To: <20240807140831.27558-3-npratte@iol.unh.edu>
On 07/08/2024 15:08, Nicholas Pratte wrote:
> Separating enums from the primary json schema might make it easier for
> incoming DTS developers and users to quickly identify what values are
> allowed in the config yaml file with relative ease. Moreover, separating
> values, such as available test suites, may streamline the test suite
> development process via a quick and simple reference to test suite
> enums.
>
> The other concern is that, as more test suites are developed, then the
> list of available test suites will become quite cumbersome. A list of
> possible test suites should be well-documented and easy to find,
> and separating test suite enums from the primary schema can achieve both
> of these needs.
>
> Signed-off-by: Nicholas Pratte <npratte@iol.unh.edu>
This is now redundant since pydantic validation has been merged. Closing.
next prev parent reply other threads:[~2025-01-08 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:08 [RFC v1 0/1] dts: separate allowed values from " Nicholas Pratte
2024-08-07 14:08 ` [RFC v1 1/1] dts: split enums from primary " Nicholas Pratte
2024-08-09 15:43 ` Jeremy Spewock
2025-01-08 10:05 ` Paul Szczepanek [this message]
2024-08-07 15:01 ` [RFC v1 0/1] dts: separate allowed values from " Luca Vizzarro
2024-09-10 9:34 ` 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=f3f795cf-369b-4467-892b-c5279f4e6623@arm.com \
--to=paul.szczepanek@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=nd@arm.com \
--cc=npratte@iol.unh.edu \
--cc=probb@iol.unh.edu \
--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).