From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: dev@dpdk.org, Paul Szczepanek <Paul.Szczepanek@arm.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] dts: improve documentation
Date: Mon, 15 Jan 2024 11:44:46 +0000 [thread overview]
Message-ID: <9dc81981-d620-475c-8a8f-ae074e583784@arm.com> (raw)
In-Reply-To: <CAOb5WZbtXrsri8v+14y+nEEH_Wa7bSyFc=bpwb3Qo28kMCkwMQ@mail.gmail.com>
On 15/01/2024 09:36, Juraj Linkeš wrote:
> This wouldn't need to be a hard requirement. It could just be a tool
> that submitters could use as a starting point (which they would
> optionally install and use).
Sorry, forgot to mention that the tool is actually a sphinx plugin,
which is used through directives in the doc pages. It doesn't actually
generate rst, but rather renders tables when running sphinx-build.
Otherwise, yeah, it would have been feasible.
> I like mappings [0] and sequences [1], as that is the standard Python
> terminology.
Ack. Sounds good to me. I could also add these links for reference.
> One more thing to like about mappings and sequences, we don't (or
> shouldn't) have to explain those. I think those would work fine on
> both fronts.
next prev parent reply other threads:[~2024-01-15 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 12:54 [PATCH] dts: improve documentation Luca Vizzarro
2024-01-04 10:52 ` Thomas Monjalon
2024-01-04 12:34 ` Luca Vizzarro
2024-01-04 13:15 ` Thomas Monjalon
2024-01-12 13:24 ` Juraj Linkeš
2024-01-12 17:16 ` Luca Vizzarro
2024-01-15 9:36 ` Juraj Linkeš
2024-01-15 11:44 ` Luca Vizzarro [this message]
2024-01-16 11:44 ` [PATCH v2 1/2] " Luca Vizzarro
2024-01-16 11:44 ` [PATCH v2 2/2] dts: add configuration schema docs Luca Vizzarro
2024-01-16 16:48 ` Juraj Linkeš
2024-01-16 16:47 ` [PATCH v2 1/2] dts: improve documentation Juraj Linkeš
2024-01-19 17:29 ` Thomas Monjalon
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=9dc81981-d620-475c-8a8f-ae074e583784@arm.com \
--to=luca.vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.