From: Dean Marx <dmarx@iol.unh.edu>
To: Patrick Robb <probb@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 v3 1/3] dts: rewrite README
Date: Mon, 14 Jul 2025 10:47:21 -0400 [thread overview]
Message-ID: <CABD7UXNK26L07EMUdrR-CH6ndh5kraVYRVfFqPGqrJaVOMCptg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUC_R_Yeoqis1cLaQJbwxyuTANYrNVpe9F=3dt29d+Wi-Q@mail.gmail.com>
> Also, I never did get a response from you about whether it would be good to include some ascii art to depict these topologies :)
>
> You don't have to be a fan, but it would be good to get your opinion. If you think it's a good idea, can you add a bugzilla ticket so we can do this during 25.11? If you're opposed I'm okay with it - ultimately the wording should make the valid topologies clear enough to people. It's not something we can add during RC4 in any case.
I like the idea of some ASCII art to illustrate the documentation
better, I'll make that Bugzilla ticket so we can add it in the next
release.
next prev parent reply other threads:[~2025-07-14 14:47 UTC|newest]
Thread overview: 26+ 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 [this message]
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-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=CABD7UXNK26L07EMUdrR-CH6ndh5kraVYRVfFqPGqrJaVOMCptg@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=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).