From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Anton Johansson <anjo@rev.ng>, qemu-devel@nongnu.org
Cc: ale@rev.ng, tsimpson@quicinc.com, bcain@quicinc.com,
mlambert@quicinc.com
Subject: Re: [PATCH] target/hexagon: Access `pkt/insn` through `ctx`
Date: Wed, 8 Feb 2023 18:28:52 +0100 [thread overview]
Message-ID: <bacfa515-cf8d-cfd1-9672-bf9357706a8e@linaro.org> (raw)
In-Reply-To: <20230208165034.21510-1-anjo@rev.ng>
On 8/2/23 17:50, Anton Johansson via wrote:
> In code emitted by idef-parser, access insn and pkt through DisasContext
> instead of explicitly taking them as arguments.
>
> Signed-off-by: Anton Johansson <anjo@rev.ng>
> ---
> target/hexagon/gen_tcg_funcs.py | 2 +-
> target/hexagon/idef-parser/parser-helpers.c | 13 ++++++-------
> 2 files changed, 7 insertions(+), 8 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-02-08 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 16:50 [PATCH] target/hexagon: Access `pkt/insn` through `ctx` Anton Johansson via
2023-02-08 17:28 ` Philippe Mathieu-Daudé [this message]
2023-02-08 17:37 ` 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=bacfa515-cf8d-cfd1-9672-bf9357706a8e@linaro.org \
--to=philmd@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=mlambert@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@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).