From: Cornelia Huck <cohuck@redhat.com>
To: qemu-s390x@nongnu.org
Cc: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Subject: [PATCH 0/3] s390x: improve documentation
Date: Tue, 5 May 2020 15:50:22 +0200 [thread overview]
Message-ID: <20200505135025.14614-1-cohuck@redhat.com> (raw)
The documentation for the s390x system emulation target still has quite
a bit of room for improvement, so I started adding some device documentation.
I'm not quite happy with the long command/output lines in the 3270 and
vfio-ccw sections, but don't know how to make that more readable. Suggestions
welcome.
Cornelia Huck (3):
docs/s390x: document the virtual css
docs/s390x: document 3270
docs/s390x: document vfio-ccw
docs/system/s390x/3270.rst | 32 +++++++++++++++++
docs/system/s390x/css.rst | 64 ++++++++++++++++++++++++++++++++++
docs/system/s390x/vfio-ccw.rst | 58 ++++++++++++++++++++++++++++++
docs/system/target-s390x.rst | 3 ++
4 files changed, 157 insertions(+)
create mode 100644 docs/system/s390x/3270.rst
create mode 100644 docs/system/s390x/css.rst
create mode 100644 docs/system/s390x/vfio-ccw.rst
--
2.21.3
next reply other threads:[~2020-05-05 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:50 Cornelia Huck [this message]
2020-05-05 13:50 ` [PATCH 1/3] docs/s390x: document the virtual css Cornelia Huck
2020-05-15 7:04 ` Thomas Huth
2020-05-15 8:51 ` Cornelia Huck
2020-05-15 8:57 ` Thomas Huth
2020-05-15 9:40 ` Cornelia Huck
2020-05-05 13:50 ` [PATCH 2/3] docs/s390x: document 3270 Cornelia Huck
2020-05-15 7:29 ` Thomas Huth
2020-05-15 9:00 ` Cornelia Huck
2020-05-15 9:14 ` Thomas Huth
2020-05-15 9:45 ` Cornelia Huck
2020-05-15 10:01 ` Thomas Huth
2020-05-05 13:50 ` [PATCH 3/3] docs/s390x: document vfio-ccw Cornelia Huck
2020-05-15 7:54 ` Thomas Huth
2020-05-15 9:15 ` Cornelia Huck
2020-05-14 6:13 ` [PATCH 0/3] s390x: improve documentation 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=20200505135025.14614-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).