From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>
Subject: Re: [RFC PATCH] docs/system: clean up code escape for riscv virt platform
Date: Tue, 06 Sep 2022 13:26:34 +0100 [thread overview]
Message-ID: <87r10ok7sk.fsf@linaro.org> (raw)
In-Reply-To: <CAKmqyKPtuT+BT7S=G3v05=s00p4OE8X+tNaccNsN7sn3yJwbcw@mail.gmail.com>
Alistair Francis <alistair23@gmail.com> writes:
> On Mon, Sep 5, 2022 at 6:39 PM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> The example code is rendered slightly mangled due to missing code
>> block. Properly escape the code block and add shell prompt and qemu to
>> fit in with the other examples on the page.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Are you going to queue via your tree?
--
Alex Bennée
next prev parent reply other threads:[~2022-09-06 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 16:39 [RFC PATCH] docs/system: clean up code escape for riscv virt platform Alex Bennée
2022-09-06 11:37 ` Alistair Francis
2022-09-06 12:26 ` Alex Bennée [this message]
2022-09-08 9:19 ` Alistair Francis
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=87r10ok7sk.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alistair23@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).