From: <ltaylorsimpson@gmail.com>
To: "'Brian Cain'" <bcain@quicinc.com>, <qemu-devel@nongnu.org>
Cc: <quic_mathbern@quicinc.com>, <sidneym@quicinc.com>,
<quic_mliebel@quicinc.com>,
"'Laurent Vivier'" <laurent@vivier.eu>
Subject: RE: [PATCH 1/3] target/hexagon: Rename HEX_EXCP_ => HEX_EVENT_
Date: Fri, 16 Aug 2024 15:31:54 -0600 [thread overview]
Message-ID: <019a01daf023$b72a1140$257e33c0$@gmail.com> (raw)
In-Reply-To: <20240816190620.1418311-1-bcain@quicinc.com>
> -----Original Message-----
> From: Brian Cain <bcain@quicinc.com>
> Sent: Friday, August 16, 2024 1:06 PM
> To: qemu-devel@nongnu.org
> Cc: bcain@quicinc.com; quic_mathbern@quicinc.com;
> sidneym@quicinc.com; quic_mliebel@quicinc.com;
> ltaylorsimpson@gmail.com; Laurent Vivier <laurent@vivier.eu>
> Subject: [PATCH 1/3] target/hexagon: Rename HEX_EXCP_ => HEX_EVENT_
>
> Change the name of these definitions to reflect that they correspond to the
> event code for the exception.
>
> Signed-off-by: Brian Cain <bcain@quicinc.com>
> ---
> linux-user/hexagon/cpu_loop.c | 4 ++--
> target/hexagon/cpu.h | 2 +-
> target/hexagon/cpu_bits.h | 14 +++++++-------
> target/hexagon/gen_tcg.h | 2 +-
> target/hexagon/translate.c | 6 +++---
> 5 files changed, 14 insertions(+), 14 deletions(-)
Reviewed-by: Taylor Simpson <ltaylorsimpson@gmail.com>
prev parent reply other threads:[~2024-08-16 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 19:06 [PATCH 1/3] target/hexagon: Rename HEX_EXCP_ => HEX_EVENT_ Brian Cain
2024-08-16 19:06 ` [PATCH 2/3] target/hexagon: rename HEX_EVENT_TRAP0=>HEX_CAUSE_TRAP0 Brian Cain
2024-08-16 21:31 ` ltaylorsimpson
2024-08-16 19:06 ` [PATCH 3/3] target/hexagon: add enums for event, cause Brian Cain
2024-08-16 21:32 ` ltaylorsimpson
2024-08-16 21:31 ` ltaylorsimpson [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='019a01daf023$b72a1140$257e33c0$@gmail.com' \
--to=ltaylorsimpson@gmail.com \
--cc=bcain@quicinc.com \
--cc=laurent@vivier.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.