From: Fabiano Rosas <farosas@suse.de>
To: Alistair Francis <alistair23@gmail.com>,
Ivan Klokov <ivan.klokov@syntacore.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org, palmer@dabbelt.com,
alistair.francis@wdc.com, bmeng.cn@gmail.com,
liwei1518@gmail.com, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com, lvivier@redhat.com,
pbonzini@redhat.com
Subject: Re: [PATCH v9 0/2] Support RISC-V CSR read/write in Qtest environment
Date: Fri, 31 Jan 2025 09:19:47 -0300 [thread overview]
Message-ID: <87o6znkwf0.fsf@suse.de> (raw)
In-Reply-To: <CAKmqyKNgPj+o3X6rN5-ru2jMfH3VHPLP094CAhbDA8_JJEE+gA@mail.gmail.com>
Alistair Francis <alistair23@gmail.com> writes:
> On Thu, Jan 9, 2025 at 7:13 PM Ivan Klokov <ivan.klokov@syntacore.com> wrote:
>>
>> These patches add functionality for unit testing RISC-V-specific registers.
>> The first patch adds a Qtest backend, and the second implements a simple test.
>>
>> ---
>> v9:
>> - Fix build errors.
>> v8:
>> - Delete RFC label.
>> v7:
>> - Fix build errors, add Reviewed-by, Acked-by.
>> ---
>>
>> Ivan Klokov (2):
>> target/riscv: Add RISC-V CSR qtest support
>> tests/qtest: QTest example for RISC-V CSR register
>
> Do you mind rebasing on
> https://github.com/alistair23/qemu/tree/riscv-to-apply.next ?
>
This was already merged via the qtest tree. I forgot to post a message
to this thread, sorry.
prev parent reply other threads:[~2025-01-31 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 9:10 [PATCH v9 0/2] Support RISC-V CSR read/write in Qtest environment Ivan Klokov
2025-01-09 9:10 ` [PATCH v9 1/2] target/riscv: Add RISC-V CSR qtest support Ivan Klokov
2025-01-09 9:10 ` [PATCH v9 2/2] tests/qtest: QTest example for RISC-V CSR register Ivan Klokov
2025-01-31 0:36 ` [PATCH v9 0/2] Support RISC-V CSR read/write in Qtest environment Alistair Francis
2025-01-31 12:19 ` Fabiano Rosas [this message]
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=87o6znkwf0.fsf@suse.de \
--to=farosas@suse.de \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=ivan.klokov@syntacore.com \
--cc=liwei1518@gmail.com \
--cc=lvivier@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).