From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 0/4] Linux user for 5.2 patches
Date: Thu, 5 Nov 2020 08:08:33 +0100 [thread overview]
Message-ID: <20201105070837.558332-1-laurent@vivier.eu> (raw)
The following changes since commit 8680d6e36468f1ca00e2fe749bef50585d632401:
Merge remote-tracking branch 'remotes/nvme/tags/pull-nvme-20201102' into st=
aging (2020-11-02 17:17:29 +0000)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-for-5.2-pull-request
for you to fetch changes up to 022625a8ade3005addb42700a145bae6a1653240:
linux-user: Check copy_from_user() return value in vma_dump_size() (2020-11=
-04 22:28:05 +0100)
----------------------------------------------------------------
Coverity and compiler warning fixes
----------------------------------------------------------------
Alistair Francis (1):
linux-user/syscall: Fix missing target_to_host_timespec64() check
Chen Qun (1):
linux-user/mips/cpu_loop: silence the compiler warnings
Peter Maydell (2):
linux-user: Use "!=3D 0" when checking if MAP_FIXED_NOREPLACE is
non-zero
linux-user: Check copy_from_user() return value in vma_dump_size()
linux-user/elfload.c | 7 +++++--
linux-user/mips/cpu_loop.c | 4 ++++
linux-user/syscall.c | 4 +++-
3 files changed, 12 insertions(+), 3 deletions(-)
--=20
2.28.0
next reply other threads:[~2020-11-05 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 7:08 Laurent Vivier [this message]
2020-11-05 7:08 ` [PULL 1/4] linux-user/mips/cpu_loop: silence the compiler warnings Laurent Vivier
2020-11-05 7:08 ` [PULL 2/4] linux-user: Use "!= 0" when checking if MAP_FIXED_NOREPLACE is non-zero Laurent Vivier
2020-11-05 7:08 ` [PULL 3/4] linux-user/syscall: Fix missing target_to_host_timespec64() check Laurent Vivier
2020-11-05 7:08 ` [PULL 4/4] linux-user: Check copy_from_user() return value in vma_dump_size() Laurent Vivier
2020-11-05 7:15 ` [PULL 0/4] Linux user for 5.2 patches no-reply
2020-11-06 9:40 ` Peter Maydell
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=20201105070837.558332-1-laurent@vivier.eu \
--to=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;
as well as URLs for NNTP newsgroup(s).