From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH] libqos/qgraph: format qgraph comments for sphinx documentation
Date: Wed, 24 Feb 2021 11:59:00 +0100 [thread overview]
Message-ID: <919d2c24-92f8-53e8-5598-97166add3083@redhat.com> (raw)
In-Reply-To: <ec53c449-b719-07cf-0993-352bdbd32725@redhat.com>
On 24/02/2021 11:49, Paolo Bonzini wrote:
> On 24/02/21 11:18, Emanuele Giuseppe Esposito wrote:
>> qtest
>> + qgraph
>
> It may make sense to add instead a "toctree" directive in qtest.rst. I
> haven't checked what the result looks like, though.
Current result is
- QTest Device Emulation Testing Framework
- Qtest Driver Framework
but I agree, maybe with an internal toctree in qtest.rst it will be
clearer. I'll try.
>
>> + * DOC: Qtest Driver Framework
>
> Is this needed since you have the heading already in qgraph.rst?
No, sorry I was experimenting and looking at qtest.rst
I forgot to remove it
>
> (Also, the whole section could move to qgraph.rst. This is what was
> done with qom.rst for example).
Ok makes sense.
>
>> + * More specifically:
>> + *
>> + * .. code::
>> + *
>> + * x86_64/pc -->contains--> other_node <--consumes-- my_driver
>> + * |
>
> You can end a paragraph with "::", and the following block will
> automatically become monospaced.
>
> Also "-->contains-->" has an extra ">" sign.
>
>> + * ``"-netdev something -device my_node,addr=04.0 -device other"``
>
> Maybe the quotes can be removed since you have monospaced text.
>
> The main issue with the text overall is that it was written before
> having experience with developing QGraph drivers and interfaces. It's
> already a good thing to have it in the manual, so the smallest possible
> change (as you did in this patch) is already an improvement.
>
> However, it would also be nice to replace the examples with something
> more "real world", based on the code in tests/qtest.
I will try to use better examples and post v2, thank you for the feedback.
Emanuele
>
> Thanks!
>
> Paolo
>
next prev parent reply other threads:[~2021-02-24 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 10:18 [PATCH] libqos/qgraph: format qgraph comments for sphinx documentation Emanuele Giuseppe Esposito
2021-02-24 10:49 ` Paolo Bonzini
2021-02-24 10:59 ` Emanuele Giuseppe Esposito [this message]
2021-02-25 8:22 ` Emanuele Giuseppe Esposito
2021-02-25 10:05 ` Paolo Bonzini
2021-02-25 10:13 ` Emanuele Giuseppe Esposito
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=919d2c24-92f8-53e8-5598-97166add3083@redhat.com \
--to=eesposit@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).