From: Dean Marx <dmarx@iol.unh.edu>
To: dev@dpdk.org
Cc: luca.vizzarro@arm.com, thomas@monjalon.net, probb@iol.unh.edu,
paul.szczepanek@arm.com, Honnappa.Nagarahalli@arm.com,
thomas.wilks@arm.com, yoan.picchi@foss.arm.com,
stephen@networkplumber.org
Subject: Re: [PATCH] doc: elaborate on per test suite configuration dts docs
Date: Thu, 5 Jun 2025 14:54:15 -0400 [thread overview]
Message-ID: <CABD7UXP_j7R9wPjPw62aPw2Ev40ujNiPBKjuOvUCLNDGzwRf8w@mail.gmail.com> (raw)
In-Reply-To: <20250516202600.632070-2-npratte@iol.unh.edu>
On Fri, May 16, 2025 at 4:26 PM Nicholas Pratte <npratte@iol.unh.edu> wrote:
>
> Introduce some additional documentation explaing the per test suite
> configuration component of DTS as the current dts documentation does
> not provide a quick access reference guide or explanation.
>
> Signed-off-by: Nicholas Pratte <npratte@iol.unh.edu>
explaining is misspelled in the commit message
<snip>
> + Test suites may also be configured individually using a provided configuration file,
> + provided at the command line, for custom configuration. The configuration file is a simple
> + mapping of test suite names to their corresponding configurations.
This part is a little odd, the words configured/configuration and
provided are used a lot. Maybe something like this would be better:
"Test suites may also be configured individually using a file provided
at the command line. This file is a simple mapping of test suite names
to their corresponding configurations."
Reviewed-by: Dean Marx <dmarx@iol.unh.edu>
next prev parent reply other threads:[~2025-06-05 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 20:26 Nicholas Pratte
2025-06-05 18:54 ` Dean Marx [this message]
2025-06-16 16:15 ` Luca Vizzarro
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=CABD7UXP_j7R9wPjPw62aPw2Ev40ujNiPBKjuOvUCLNDGzwRf8w@mail.gmail.com \
--to=dmarx@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.org \
--cc=thomas.wilks@arm.com \
--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).