From: "Björn Töpel" <bjorn@kernel.org>
To: Alexandre Ghiti <alexghiti@rivosinc.com>,
Jonathan Corbet <corbet@lwn.net>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>
Subject: Re: [PATCH 1/2] Documentation: riscv: Add early boot document
Date: Mon, 19 Jun 2023 13:00:51 +0200 [thread overview]
Message-ID: <87sfanbtss.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20230619094705.51337-1-alexghiti@rivosinc.com>
Alexandre Ghiti <alexghiti@rivosinc.com> writes:
> This document describes the constraints and requirements of the early
> boot process in a RISC-V kernel.
>
> Szigned-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Additional 'z'; "Signed-off-by:"
Nice writeup!
Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
next prev parent reply other threads:[~2023-06-19 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:47 [PATCH 1/2] Documentation: riscv: Add early boot document Alexandre Ghiti
2023-06-19 9:47 ` [PATCH 2/2] Documentation: riscv: Update boot image header since EFI stub is supported Alexandre Ghiti
2023-06-19 18:58 ` Atish Patra
2023-06-19 9:49 ` [PATCH 1/2] Documentation: riscv: Add early boot document Alexandre Ghiti
2023-06-20 7:18 ` Sunil V L
2023-06-20 8:14 ` Alexandre Ghiti
2023-06-19 11:00 ` Björn Töpel [this message]
2023-06-19 12:25 ` Conor Dooley
2023-06-19 14:04 ` Alexandre Ghiti
2023-06-19 16:00 ` Conor Dooley
2023-06-19 16:48 ` Jonathan Corbet
2023-06-20 9:57 ` Conor Dooley
2023-06-20 9:09 ` Alexandre Ghiti
2023-06-20 10:33 ` Conor Dooley
2023-06-20 12:00 ` Alexandre Ghiti
2023-06-20 7:41 ` Sunil V L
2023-06-20 8:24 ` Alexandre Ghiti
2023-06-20 10:31 ` Song Shuai
2023-06-20 12:06 ` Alexandre Ghiti
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=87sfanbtss.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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