From: Peter Maydell <peter.maydell@linaro.org>
To: Helge Deller <deller@gmx.de>
Cc: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
Richard Henderson <richard.henderson@linaro.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PULL 00/12] Publish1 patches
Date: Thu, 22 Sep 2022 10:37:24 +0100 [thread overview]
Message-ID: <CAFEAcA8cwqSeYooqFSE4Xa1_4XCC8+gTSU9oLfNXHKE+YkDZKA@mail.gmail.com> (raw)
In-Reply-To: <20220920173152.199359-1-deller@gmx.de>
On Wed, 21 Sept 2022 at 00:00, Helge Deller <deller@gmx.de> wrote:
>
> The following changes since commit 621da7789083b80d6f1ff1c0fb499334007b4f51:
>
> Update version for v7.1.0 release (2022-08-30 09:40:11 -0700)
>
> are available in the Git repository at:
>
> https://github.com/hdeller/qemu-hppa.git tags/publish1-pull-request
>
> for you to fetch changes up to 7f8674a61a908592bb4e8e698f5bef84d0eeb8cc:
>
> linux-user: Add parameters of getrandom() syscall for strace (2022-09-18 21:35:27 +0200)
>
> ----------------------------------------------------------------
> linux-user: Add more syscalls, enhance tracing & logging enhancements
>
> Here is a bunch of patches for linux-user.
>
> Most of them add missing syscalls and enhance the tracing/logging.
> Some of the patches are target-hppa specific.
> I've tested those on productive hppa debian buildd servers (running qemu-user).
Maybe I've missed some context in previous mailing list threads,
but I think overall it would be better for linux-user patches to
go through the linux-user tree; most of these don't seem hppa
specific.
thanks
-- PMM
next prev parent reply other threads:[~2022-09-22 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:31 [PULL 00/12] Publish1 patches Helge Deller
2022-09-20 17:31 ` [PULL 01/12] linux-user: Add missing signals in strace output Helge Deller
2022-09-20 17:31 ` [PULL 02/12] linux-user: Add missing clock_gettime64() syscall strace Helge Deller
2022-09-20 17:31 ` [PULL 03/12] linux-user: Add pidfd_open(), pidfd_send_signal() and pidfd_getfd() syscalls Helge Deller
2022-09-20 17:31 ` [PULL 04/12] linux-user: Log failing executable in EXCP_DUMP() Helge Deller
2022-09-20 17:31 ` [PULL 05/12] linux-user/hppa: Use EXCP_DUMP() to show enhanced debug info Helge Deller
2022-09-20 17:31 ` [PULL 06/12] linux-user/hppa: Dump IIR on register dump Helge Deller
2022-09-20 17:31 ` [PULL 07/12] linux-user: Fix strace of chmod() if mode == 0 Helge Deller
2022-09-20 17:31 ` [PULL 08/12] linux-user/hppa: Set TASK_UNMAPPED_BASE to 0xfa000000 for hppa arch Helge Deller
2022-09-20 17:31 ` [PULL 09/12] linux-user: Add strace for clock_nanosleep() Helge Deller
2022-09-20 17:31 ` [PULL 10/12] linux-user: Show timespec on strace for futex() Helge Deller
2022-09-20 17:31 ` [PULL 11/12] linux-user: Add close_range() syscall Helge Deller
2022-09-20 17:31 ` [PULL 12/12] linux-user: Add parameters of getrandom() syscall for strace Helge Deller
2022-09-21 17:59 ` [PULL 00/12] Publish1 patches Philippe Mathieu-Daudé via
2022-09-22 9:37 ` Peter Maydell [this message]
2022-09-22 13:00 ` Laurent Vivier
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=CAFEAcA8cwqSeYooqFSE4Xa1_4XCC8+gTSU9oLfNXHKE+YkDZKA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@gmail.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).