From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH v2 0/3] some docs (booting, mttcg, icount)
Date: Wed, 1 Jul 2020 17:11:50 +0100 [thread overview]
Message-ID: <20200701161153.30988-1-alex.bennee@linaro.org> (raw)
Hi,
This is the current state of documentation patches. They didn't get
much review the first time around so I present them as a series. I
Think we should merge them unless anyone want to argue they actively
muddy our document situation?
The following have no reviews:
- docs/devel: convert and update MTTCG design document
- docs/booting.rst: start documenting the boot process
Alex Bennée (3):
docs/booting.rst: start documenting the boot process
docs/devel: convert and update MTTCG design document
docs/devel: add some notes on tcg-icount for developers
docs/devel/index.rst | 2 +
...ti-thread-tcg.txt => multi-thread-tcg.rst} | 52 +++---
docs/devel/tcg-icount.rst | 89 ++++++++++
docs/interop/booting.rst | 159 ++++++++++++++++++
docs/interop/index.rst | 1 +
5 files changed, 284 insertions(+), 19 deletions(-)
rename docs/devel/{multi-thread-tcg.txt => multi-thread-tcg.rst} (90%)
create mode 100644 docs/devel/tcg-icount.rst
create mode 100644 docs/interop/booting.rst
--
2.20.1
next reply other threads:[~2020-07-01 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 16:11 Alex Bennée [this message]
2020-07-01 16:11 ` [PATCH v2 1/3] docs/booting.rst: start documenting the boot process Alex Bennée
2020-07-01 19:45 ` Richard Henderson
2020-07-03 15:26 ` Peter Maydell
2020-07-03 16:55 ` Alex Bennée
2020-07-01 16:11 ` [PATCH v2 2/3] docs/devel: convert and update MTTCG design document Alex Bennée
2020-07-01 19:50 ` Richard Henderson
2020-07-01 16:11 ` [PATCH v2 3/3] docs/devel: add some notes on tcg-icount for developers Alex Bennée
2020-07-03 15:41 ` Peter Maydell
2020-07-01 16:55 ` [PATCH v2 0/3] some docs (booting, mttcg, icount) no-reply
2020-07-01 16:56 ` no-reply
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=20200701161153.30988-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@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).