From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Brian Cain <bcain@quicinc.com>, qemu-devel@nongnu.org
Cc: quic_mathbern@quicinc.com, sidneym@quicinc.com,
quic_mliebel@quicinc.com, ltaylorsimpson@gmail.com
Subject: Re: [PATCH] target/hexagon: define a v66 CPU
Date: Wed, 31 Jul 2024 10:40:32 +0200 [thread overview]
Message-ID: <0480fbc8-4108-4060-a5dc-9ef6cbbae33c@linaro.org> (raw)
In-Reply-To: <20240731010954.1959253-1-bcain@quicinc.com>
On 31/7/24 03:09, Brian Cain wrote:
> For now, v66 behavior is the same as other CPUs.
>
> Signed-off-by: Brian Cain <bcain@quicinc.com>
> ---
> target/hexagon/cpu-qom.h | 1 +
> target/hexagon/cpu.c | 2 ++
> 2 files changed, 3 insertions(+)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-07-31 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 1:09 [PATCH] target/hexagon: define a v66 CPU Brian Cain
2024-07-31 8:40 ` Philippe Mathieu-Daudé [this message]
2024-07-31 16:37 ` ltaylorsimpson
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=0480fbc8-4108-4060-a5dc-9ef6cbbae33c@linaro.org \
--to=philmd@linaro.org \
--cc=bcain@quicinc.com \
--cc=ltaylorsimpson@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quic_mathbern@quicinc.com \
--cc=quic_mliebel@quicinc.com \
--cc=sidneym@quicinc.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).