From: Taylor Simpson <ltaylorsimpson@gmail.com>
To: Brian Cain <brian.cain@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, richard.henderson@linaro.org,
philmd@linaro.org, matheus.bernardino@oss.qualcomm.com,
ale@rev.ng, anjo@rev.ng, marco.liebel@oss.qualcomm.com,
alex.bennee@linaro.org, quic_mburton@quicinc.com,
sid.manning@oss.qualcomm.com
Subject: Re: [PATCH v2 4/4] tests/tcg/hexagon: Add cs{0,1} coverage
Date: Thu, 9 Oct 2025 15:40:11 -0600 [thread overview]
Message-ID: <CAATN3NrsWN_PPHx2Qxn-QEH-Ov0CDxTUERdScPLi-M8nRNtr8w@mail.gmail.com> (raw)
In-Reply-To: <20251009195943.438454-5-brian.cain@oss.qualcomm.com>
On Thu, Oct 9, 2025 at 1:59 PM Brian Cain <brian.cain@oss.qualcomm.com> wrote:
>
> Cover cs0,1 register corruption in the signal_context test case.
>
> Reviewed-by: Anton Johansson <anjo@rev.ng>
> Signed-off-by: Brian Cain <brian.cain@oss.qualcomm.com>
> ---
> tests/tcg/hexagon/signal_context.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
Did you see my previous feedback on this?
next prev parent reply other threads:[~2025-10-09 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 19:59 [PATCH v2 0/4] hexagon: Fixes to sigcontext Brian Cain
2025-10-09 19:59 ` [PATCH v2 1/4] linux-user/hexagon: Fix sigcontext Brian Cain
2025-10-09 21:36 ` Taylor Simpson
2025-10-09 19:59 ` [PATCH v2 2/4] linux-user/hexagon: use abi_ulong Brian Cain
2025-10-09 20:22 ` Philippe Mathieu-Daudé
2025-10-09 21:37 ` Taylor Simpson
2025-10-09 19:59 ` [PATCH v2 3/4] linux-user/hexagon: Use an array for GPRs Brian Cain
2025-10-09 20:22 ` Philippe Mathieu-Daudé
2025-10-09 21:38 ` Taylor Simpson
2025-10-09 19:59 ` [PATCH v2 4/4] tests/tcg/hexagon: Add cs{0,1} coverage Brian Cain
2025-10-09 21:40 ` Taylor Simpson [this message]
2025-10-09 20:07 ` [PATCH v2 0/4] hexagon: Fixes to sigcontext Richard Henderson
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=CAATN3NrsWN_PPHx2Qxn-QEH-Ov0CDxTUERdScPLi-M8nRNtr8w@mail.gmail.com \
--to=ltaylorsimpson@gmail.com \
--cc=ale@rev.ng \
--cc=alex.bennee@linaro.org \
--cc=anjo@rev.ng \
--cc=brian.cain@oss.qualcomm.com \
--cc=marco.liebel@oss.qualcomm.com \
--cc=matheus.bernardino@oss.qualcomm.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quic_mburton@quicinc.com \
--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).