From: Patrick Robb <probb@iol.unh.edu>
To: Dean Marx <dmarx@iol.unh.edu>
Cc: luca.vizzarro@arm.com, yoan.picchi@foss.arm.com,
Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com,
dev@dpdk.org
Subject: Re: [PATCH v4 1/3] dts: rewrite README
Date: Tue, 15 Jul 2025 17:52:31 -0400 [thread overview]
Message-ID: <CAJvnSUCjRspat=S+A6jSH+tvhPBZ7Re8nUM1WE62sVN9Jq7z3g@mail.gmail.com> (raw)
In-Reply-To: <20250714171346.564267-1-dmarx@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Mon, Jul 14, 2025 at 1:13 PM Dean Marx <dmarx@iol.unh.edu> wrote:
>
> +
> +# Simple Linux Setup
> +
> +1. On your TG and SUT nodes, add a dedicated user. In this example I will
> add a dedicated user for DTS.
>
This is getting away from what I was suggesting. The original version was:
On your TG and SUT nodes, add a dedicated user. In this example I will name
the user "dts."
And it's English semantics but what I was getting at is if you are going to
call a user "dedicated" you have to say what for. I don't like that you
have now removed the "In this example I will name the user "dts." line
because that's really important info. So in my opinion the final version
should be like:
On your TG and SUT nodes, add a dedicated user for DTS. In this example I
will name the user "dts."
>
>
>
[-- Attachment #2: Type: text/html, Size: 1531 bytes --]
next prev parent reply other threads:[~2025-07-15 21:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 15:37 [PATCH v1 " Dean Marx
2025-05-27 15:37 ` [PATCH v1 2/3] dts: rewrite dts rst Dean Marx
2025-05-28 21:25 ` Patrick Robb
2025-05-29 12:27 ` Paul Szczepanek
2025-06-03 17:28 ` [PATCH v2 1/2] dts: rewrite README Dean Marx
2025-06-03 17:28 ` [PATCH v2 2/2] dts: rewrite dts rst Dean Marx
2025-06-25 4:07 ` Patrick Robb
2025-07-09 19:57 ` Thomas Monjalon
2025-07-11 14:58 ` Patrick Robb
2025-06-25 4:06 ` [PATCH v2 1/2] dts: rewrite README Patrick Robb
2025-07-11 17:24 ` [PATCH v3 1/3] " Dean Marx
2025-07-11 17:24 ` [PATCH v3 2/3] doc: rephrase terminology in dts.rst Dean Marx
2025-07-14 14:10 ` Patrick Robb
2025-07-11 17:24 ` [PATCH v3 3/3] doc: revise coding guidelines section Dean Marx
2025-07-14 16:22 ` Patrick Robb
2025-07-11 21:22 ` [PATCH v3 1/3] dts: rewrite README Patrick Robb
2025-07-14 14:47 ` Dean Marx
2025-07-14 17:13 ` [PATCH v4 " Dean Marx
2025-07-14 17:13 ` [PATCH v4 2/3] doc: rephrase terminology in dts.rst Dean Marx
2025-07-14 17:13 ` [PATCH v4 3/3] doc: revise coding guidelines section Dean Marx
2025-07-15 22:25 ` Patrick Robb
2025-07-15 21:52 ` Patrick Robb [this message]
2025-05-27 15:37 ` [PATCH v1 3/3] dts: fix doc generation bug Dean Marx
2025-05-28 20:28 ` Patrick Robb
2025-05-29 12:28 ` Paul Szczepanek
2025-05-28 20:40 ` [PATCH v1 1/3] dts: rewrite README Patrick Robb
2025-05-29 12:27 ` Paul Szczepanek
2025-05-29 12:40 ` Paul Szczepanek
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='CAJvnSUCjRspat=S+A6jSH+tvhPBZ7Re8nUM1WE62sVN9Jq7z3g@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@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).