From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: anjo@rev.ng, thuth@redhat.com
Subject: Re: [PATCH v2 1/5] disas: Move disas.c to disas/
Date: Wed, 10 May 2023 17:12:27 +0200 [thread overview]
Message-ID: <2bc20d18-f250-dfb1-ba0f-58e97d962373@linaro.org> (raw)
In-Reply-To: <20230509163326.121090-2-richard.henderson@linaro.org>
On 9/5/23 18:33, Richard Henderson wrote:
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> Message-Id: <20230503072331.1747057-80-richard.henderson@linaro.org>
> ---
> meson.build | 3 ---
> disas.c => disas/disas.c | 0
> disas/meson.build | 4 +++-
> 3 files changed, 3 insertions(+), 4 deletions(-)
> rename disas.c => disas/disas.c (100%)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-05-10 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 16:33 [PATCH v2 0/5] Make the core disassembler functions target-independent Richard Henderson
2023-05-09 16:33 ` [PATCH v2 1/5] disas: Move disas.c to disas/ Richard Henderson
2023-05-10 15:12 ` Philippe Mathieu-Daudé [this message]
2023-05-09 16:33 ` [PATCH v2 2/5] disas: Remove target_ulong from the interface Richard Henderson
2023-05-10 6:48 ` Thomas Huth
2023-05-09 16:33 ` [PATCH v2 3/5] disas: Remove target-specific headers Richard Henderson
2023-05-09 16:33 ` [PATCH v2 4/5] disas: Move softmmu specific code to separate file Richard Henderson
2023-05-09 16:33 ` [PATCH v2 5/5] disas: Move disas.c into the target-independent source set Richard Henderson
2023-05-10 6:53 ` Thomas Huth
2023-05-10 7:46 ` Richard Henderson
2023-05-10 8:10 ` Thomas Huth
2023-05-10 8:13 ` Richard Henderson
2023-05-10 15:19 ` Philippe Mathieu-Daudé
2023-05-10 6:54 ` [PATCH v2 0/5] Make the core disassembler functions target-independent Thomas Huth
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=2bc20d18-f250-dfb1-ba0f-58e97d962373@linaro.org \
--to=philmd@linaro.org \
--cc=anjo@rev.ng \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).