From: Laurent Vivier <laurent@vivier.eu>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Helge Deller" <deller@gmx.de>, "Drew DeVault" <sir@cmpwn.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v5 3/5] linux-user/strace: Add output for execveat() syscall
Date: Wed, 25 Jan 2023 10:33:14 +0100 [thread overview]
Message-ID: <5ec7f95c-df5c-c8f8-1542-ad4aa5befbf9@vivier.eu> (raw)
In-Reply-To: <20221104173632.1052-4-philmd@linaro.org>
Le 04/11/2022 à 18:36, Philippe Mathieu-Daudé a écrit :
> From: Drew DeVault <sir@cmpwn.com>
>
> Signed-off-by: Drew DeVault <sir@cmpwn.com>
> Message-Id: <20221104081015.706009-1-sir@cmpwn.com>
> Suggested-by: Helge Deller <deller@gmx.de>
> [PMD: Split of bigger patch]
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> linux-user/strace.c | 23 +++++++++++++++++++++++
> linux-user/strace.list | 2 +-
> 2 files changed, 24 insertions(+), 1 deletion(-)
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2023-01-25 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 17:36 [PATCH v5 0/5] linux-user: implement execveat Philippe Mathieu-Daudé
2022-11-04 17:36 ` [PATCH v5 1/5] linux-user/strace: Constify struct flags Philippe Mathieu-Daudé
2023-01-25 9:20 ` Laurent Vivier
2022-11-04 17:36 ` [PATCH v5 2/5] linux-user/strace: Extract print_execve_argv() from print_execve() Philippe Mathieu-Daudé
2023-01-25 9:28 ` Laurent Vivier
2022-11-04 17:36 ` [PATCH v5 3/5] linux-user/strace: Add output for execveat() syscall Philippe Mathieu-Daudé
2023-01-25 9:33 ` Laurent Vivier [this message]
2022-11-04 17:36 ` [PATCH v5 4/5] linux-user/syscall: Extract do_execve() from do_syscall1() Philippe Mathieu-Daudé
2023-01-25 9:36 ` Laurent Vivier
2022-11-04 17:36 ` [PATCH v5 5/5] linux-user/syscall: Implement execveat() Philippe Mathieu-Daudé
2023-01-25 9:46 ` [PATCH v5 0/5] linux-user: implement execveat Laurent Vivier
2023-01-25 9:47 ` Drew DeVault
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=5ec7f95c-df5c-c8f8-1542-ad4aa5befbf9@vivier.eu \
--to=laurent@vivier.eu \
--cc=berrange@redhat.com \
--cc=deller@gmx.de \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sir@cmpwn.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).