From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH] linux-user: Drop uint and ulong
Date: Thu, 11 May 2023 12:15:06 +0200 [thread overview]
Message-ID: <d78c62dc-18f8-4962-96bf-3729607ad5bd@linaro.org> (raw)
In-Reply-To: <20230511085056.13809-1-quintela@redhat.com>
On 11/5/23 10:50, Juan Quintela wrote:
> These are types not used anymore anywhere else.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> linux-user/mmap.c | 2 +-
> linux-user/syscall.c | 8 ++++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-05-11 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 8:50 [PATCH] linux-user: Drop uint and ulong Juan Quintela
2023-05-11 10:15 ` Philippe Mathieu-Daudé [this message]
2023-05-11 10:38 ` Laurent Vivier
2023-05-11 11:10 ` Juan Quintela
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=d78c62dc-18f8-4962-96bf-3729607ad5bd@linaro.org \
--to=philmd@linaro.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
/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).