From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Tony Krowiak <akrowiak@linux.ibm.com>
Cc: "Jason J . Herne" <jjherne@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Pierre Morel <pmorel@linux.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [PATCH RFC 2/2] docs: rstfy vfio-ap documentation
Date: Wed, 12 Feb 2020 15:57:00 +0100 [thread overview]
Message-ID: <20200212155700.3d0a879e.cohuck@redhat.com> (raw)
In-Reply-To: <20200207163218.207a931f.cohuck@redhat.com>
On Fri, 7 Feb 2020 16:32:18 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> On Fri, 7 Feb 2020 12:43:03 +0000
> Peter Maydell <peter.maydell@linaro.org> wrote:
>
> > On Tue, 28 Jan 2020 at 19:39, Cornelia Huck <cohuck@redhat.com> wrote:
> > >
> > > Move to system/, as this is mostly about configuring vfio-ap.
> > >
> > > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > > - Example 1: Valid configuration:
> > > - ------------------------------
> > > - Guest1: adapters 1,2 domains 5,6
> > > - Guest2: adapter 1,2 domain 7
> > > +Example 1: Valid configuration
> > > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > +Guest1: adapters 1,2 domains 5,6
> > > +Guest2: adapter 1,2 domain 7
> >
> > These don't render correctly -- rST thinks the "Example 1..." line
> > is a subsection heading because of the underlining, and then renders
> > the next two lines as runon-text:
> > "Guest1: adapters 1,2 domains 5,6 Guest2: adapter 1,2 domain 7"
> >
> > Depending on what you want, you could try one of:
> > * use a literal block (which gets you fixed-width font, preserved
> > whitespace and linebreaks)
> > * use a bulleted list
> > * use one of rST's table formats
>
> Hm... I think this is supposed to be:
> - header ("Example 1: ...")
> - config
> - explanation why this is a valid config
>
> Maybe a table? Tony, any preferences?
>
> >
> > (is it deliberate that line 1 is "adapters" and line 2 is "adapter" ?)
>
> I don't think so.
>
> >
> > > - This is valid because both guests have a unique set of APQNs: Guest1 has
> > > - APQNs (1,5), (1,6), (2,5) and (2,6); Guest2 has APQNs (1,7) and (2,7).
> > > +This is valid because both guests have a unique set of APQNs: Guest1 has
> > > +APQNs (1,5), (1,6), (2,5) and (2,6); Guest2 has APQNs (1,7) and (2,7).
This section now looks like this:
Example 1: Valid configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+----------+--------+--------+
| | Guest1 | Guest2 |
+==========+========+========+
| adapters | 1, 2 | 1, 2 |
+----------+--------+--------+
| domains | 5, 6 | 7 |
+----------+--------+--------+
This is valid because both guests have a unique set of APQNs:
* Guest1 has APQNs (1,5), (1,6), (2,5) and (2,6);
* Guest2 has APQNs (1,7) and (2,7).
Seems more readable to me, also in the rendered html. (Not sure if
switching rows/columns would be better.)
next prev parent reply other threads:[~2020-02-12 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 18:01 [PATCH RFC 0/2] docs: rstfy some s390 docs Cornelia Huck
2020-01-28 18:01 ` [PATCH RFC 1/2] docs: rstfy s390 dasd ipl documentation Cornelia Huck
2020-02-05 11:02 ` Thomas Huth
2020-02-07 12:05 ` Peter Maydell
2020-02-07 15:22 ` Cornelia Huck
2020-01-28 18:01 ` [PATCH RFC 2/2] docs: rstfy vfio-ap documentation Cornelia Huck
2020-02-05 11:05 ` Thomas Huth
2020-02-07 12:43 ` Peter Maydell
2020-02-07 15:32 ` Cornelia Huck
2020-02-12 14:57 ` Cornelia Huck [this message]
2020-02-12 15:41 ` Cornelia Huck
2020-02-05 10:51 ` [PATCH RFC 0/2] docs: rstfy some s390 docs Cornelia Huck
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=20200212155700.3d0a879e.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).