From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Alistair Francis <alistair23@gmail.com>,
Frank Chang <frank.chang@sifive.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: [PATCH v2 0/2] hw/riscv: Make CPU config error handling generous
Date: Sat, 14 May 2022 15:29:39 +0900 [thread overview]
Message-ID: <cover.1652509778.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1652435235.git.research_trasio@irq.a4lg.com>
c.f.
<https://lists.gnu.org/archive/html/qemu-riscv/2022-05/msg00229.html>
This patchset is functionally equivalent to v1 but fixes commit titles.
Tsukasa OI (2):
hw/riscv: Make CPU config error handling generous (virt/spike)
hw/riscv: Make CPU config error handling generous
(sifive_e/u/opentitan)
hw/riscv/opentitan.c | 2 +-
hw/riscv/sifive_e.c | 2 +-
hw/riscv/sifive_u.c | 4 ++--
hw/riscv/spike.c | 2 +-
hw/riscv/virt.c | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
base-commit: 178bacb66d98d9ee7a702b9f2a4dfcd88b72a9ab
--
2.34.1
next prev parent reply other threads:[~2022-05-14 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:47 [PATCH 0/2] hw/riscv: Make CPU config error handling generous Tsukasa OI
2022-05-13 9:47 ` [PATCH 1/2] target/riscv: Make CPU config error handling generous (virt/spike) Tsukasa OI
2022-05-13 9:47 ` [PATCH 2/2] target/riscv: Make CPU config error handling generous (sifive_e/u/opentitan) Tsukasa OI
2022-05-14 6:29 ` Tsukasa OI [this message]
2022-05-14 6:29 ` [PATCH v2 1/2] hw/riscv: Make CPU config error handling generous (virt/spike) Tsukasa OI
2022-05-17 0:36 ` Alistair Francis
2022-05-14 6:29 ` [PATCH v2 2/2] hw/riscv: Make CPU config error handling generous (sifive_e/u/opentitan) Tsukasa OI
2022-05-17 0:36 ` Alistair Francis
2022-05-17 1:57 ` [PATCH v2 0/2] hw/riscv: Make CPU config error handling generous 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=cover.1652509778.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=alistair23@gmail.com \
--cc=frank.chang@sifive.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).