From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com
Subject: Re: [PATCH 0/2] target/riscv: add missing riscv,isa strings
Date: Mon, 24 Jul 2023 09:12:40 -0300 [thread overview]
Message-ID: <5b3bbe94-780e-abe0-cc7b-705b067f337b@ventanamicro.com> (raw)
In-Reply-To: <CAKmqyKPzwDrtSH5_V4n=QR+CCPz6L1YqcSL+Y83fP7Fy70h-kQ@mail.gmail.com>
On 7/23/23 23:51, Alistair Francis wrote:
> On Thu, Jul 20, 2023 at 11:25 PM Daniel Henrique Barboza
> <dbarboza@ventanamicro.com> wrote:
>>
>> Hi,
>>
>> Found these 2 instances while working in more 8.2 material.
>>
>> I believe both are safe for freeze but I won't lose my sleep if we
>> decide to postpone it.
>
> I wasn't going to squeeze them into the freeze
>
>>
>> Daniel Henrique Barboza (2):
>> target/riscv/cpu.c: add zmmul isa string
>> target/riscv/cpu.c: add smepmp isa string
>
> Do you mind rebasing :)
> https://github.com/alistair23/qemu/tree/riscv-to-apply.next
:)
Thanks!
Daniel
>
> Alistair
>
>>
>> target/riscv/cpu.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> --
>> 2.41.0
>>
>>
prev parent reply other threads:[~2023-07-24 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 13:24 [PATCH 0/2] target/riscv: add missing riscv,isa strings Daniel Henrique Barboza
2023-07-20 13:24 ` [PATCH 1/2] target/riscv/cpu.c: add zmmul isa string Daniel Henrique Barboza
2023-07-21 1:37 ` Weiwei Li
2023-07-23 22:40 ` Alistair Francis
2023-07-20 13:24 ` [PATCH 2/2] target/riscv/cpu.c: add smepmp " Daniel Henrique Barboza
2023-07-21 1:37 ` Weiwei Li
2023-07-23 22:41 ` Alistair Francis
2023-07-24 2:49 ` Alistair Francis
2023-07-24 2:51 ` [PATCH 0/2] target/riscv: add missing riscv,isa strings Alistair Francis
2023-07-24 12:12 ` Daniel Henrique Barboza [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=5b3bbe94-780e-abe0-cc7b-705b067f337b@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng@tinylab.org \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.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).