From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Taylor Simpson <ltaylorsimpson@gmail.com>, qemu-devel@nongnu.org
Cc: brian.cain@oss.qualcomm.com, matheus.bernardino@oss.qualcomm.com,
sid.manning@oss.qualcomm.com, marco.liebel@oss.qualcomm.com,
richard.henderson@linaro.org, ale@rev.ng, anjo@rev.ng
Subject: Re: [PATCH 4/4] Hexagon (target/hexagon) s/log_write/gen_write
Date: Mon, 17 Nov 2025 18:37:01 +0100 [thread overview]
Message-ID: <e8938d60-23ec-4235-ab69-73cf1de2aede@linaro.org> (raw)
In-Reply-To: <20251114230013.158098-5-ltaylorsimpson@gmail.com>
On 15/11/25 00:00, Taylor Simpson wrote:
> These functions don't "log" anything, they just generate the write
>
> Signed-off-by: Taylor Simpson <ltaylorsimpson@gmail.com>
> ---
> target/hexagon/gen_tcg_funcs.py | 2 +-
> target/hexagon/hex_common.py | 30 +++++++++++++++---------------
> 2 files changed, 16 insertions(+), 16 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-11-17 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 23:00 [PATCH 0/4] Clean up end-of-instruction processing Taylor Simpson
2025-11-14 23:00 ` [PATCH 1/4] Hexagon (target/hexagon) Remove gen_log_reg_write Taylor Simpson
2025-11-14 23:00 ` [PATCH 2/4] Hexagon (target/hexagon) s/gen_log_pred_write/gen_pred_write Taylor Simpson
2025-11-17 17:35 ` Philippe Mathieu-Daudé
2025-11-14 23:00 ` [PATCH 3/4] Hexagon (target/hexagon) s/gen_log_vreg_write/gen_vreg_write Taylor Simpson
2025-11-17 17:36 ` Philippe Mathieu-Daudé
2025-11-14 23:00 ` [PATCH 4/4] Hexagon (target/hexagon) s/log_write/gen_write Taylor Simpson
2025-11-17 17:37 ` Philippe Mathieu-Daudé [this message]
2025-11-17 9:28 ` [PATCH 0/4] Clean up end-of-instruction processing Philippe Mathieu-Daudé
2025-11-17 17:08 ` Brian Cain
2025-11-17 17:35 ` Philippe Mathieu-Daudé
2025-11-17 18:35 ` Taylor Simpson
2025-11-17 20:02 ` Taylor Simpson
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=e8938d60-23ec-4235-ab69-73cf1de2aede@linaro.org \
--to=philmd@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=brian.cain@oss.qualcomm.com \
--cc=ltaylorsimpson@gmail.com \
--cc=marco.liebel@oss.qualcomm.com \
--cc=matheus.bernardino@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sid.manning@oss.qualcomm.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).