From: Helge Deller <deller@kernel.org>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>, Helge Deller <deller@gmx.de>
Subject: [PATCH 0/2] Two linux-user patches
Date: Thu, 12 Mar 2026 21:12:37 +0100 [thread overview]
Message-ID: <20260312201239.2976-1-deller@kernel.org> (raw)
From: Helge Deller <deller@gmx.de>
Two linux-user patches from Razvan Ghiorghe.
They were sent to the mailing lists but were lacking review.
I think they are OK, if other people want to review too, it would be good.
Helge
Razvan Ghiorghe (2):
linux-user: Fix zero_bss for RX PT_LOAD segments
linux-user: fix mremap with old_size=0 for shared mappings
linux-user/elfload.c | 37 +++++++++++++++++++------------
linux-user/mmap.c | 52 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 75 insertions(+), 14 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-12 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 20:12 Helge Deller [this message]
2026-03-12 20:12 ` [PATCH 1/2] linux-user: Fix zero_bss for RX PT_LOAD segments Helge Deller
2026-03-12 20:12 ` [PATCH 2/2] linux-user: fix mremap with old_size=0 for shared mappings Helge Deller
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=20260312201239.2976-1-deller@kernel.org \
--to=deller@kernel.org \
--cc=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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