From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/3] docs/booting.rst: start documenting the boot process
Date: Wed, 1 Jul 2020 12:45:51 -0700 [thread overview]
Message-ID: <56bd2532-a949-456b-bf70-025864439f41@linaro.org> (raw)
In-Reply-To: <20200701161153.30988-2-alex.bennee@linaro.org>
On 7/1/20 9:11 AM, Alex Bennée wrote:
> While working on some test cases I realised there was quite a lot of
> assumed knowledge about how things boot up. I thought it would be
> worth gathering this together in a user facing document where we could
> pour in the details and background to the boot process. As it's quite
> wordy I thought it should be a separate document to the manual (which
> can obviously reference this).
>
> The document follows the socratic method and leaves the reader to ask
> themselves some questions in an effort to elucidate them about any
> problems they may be having.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-Id: <20190308211557.22589-1-alex.bennee@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2020-07-01 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 16:11 [PATCH v2 0/3] some docs (booting, mttcg, icount) Alex Bennée
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 [this message]
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=56bd2532-a949-456b-bf70-025864439f41@linaro.org \
--to=richard.henderson@linaro.org \
--cc=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).