From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Nicholas Pratte <npratte@iol.unh.edu>,
thomas@monjalon.net, probb@iol.unh.edu, dmarx@iol.unh.edu,
paul.szczepanek@arm.com, Honnappa.Nagarahalli@arm.com,
thomas.wilks@arm.com, yoan.picchi@foss.arm.com,
stephen@networkplumber.org
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: elaborate on per test suite configuration dts docs
Date: Mon, 16 Jun 2025 17:15:24 +0100 [thread overview]
Message-ID: <1e2a1edc-23af-4c42-91aa-2c75ed2cce53@arm.com> (raw)
In-Reply-To: <20250516202600.632070-2-npratte@iol.unh.edu>
Agree with Dean's changes. Also the start marker is broken, but can
easily be added.
Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
prev parent reply other threads:[~2025-06-16 16:15 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
2025-06-16 16:15 ` Luca Vizzarro [this message]
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=1e2a1edc-23af-4c42-91aa-2c75ed2cce53@arm.com \
--to=luca.vizzarro@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--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).