From: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>
To: qemu-devel@nongnu.org
Cc: laurent@vivier.eu, Aleksandar Markovic <amarkovic@wavecomp.com>
Subject: [PATCH v2 0/9] linux-user: Update syscall numbers to kernel 5.5 level
Date: Thu, 13 Feb 2020 02:46:24 +0100 [thread overview]
Message-ID: <1581558393-9182-1-git-send-email-aleksandar.markovic@rt-rk.com> (raw)
From: Aleksandar Markovic <amarkovic@wavecomp.com>
v1->v2:
- corrected mips parts based on Laurent's review
This series is a spin-off of another larger linux-user series
that become too large to handle, hence these patches related to
syscall numbers are now in this, separate, series.
This series covers updating syscall numbers defined in the following
files:
- linux-user/alpha/syscall_nr.h
- linux-user/arm/syscall_nr.h
- linux-user/m68k/syscall_nr.h
- linux-user/microblaze/syscall_nr.h
- linux-user/mips/cpu_loop.c
- linux-user/mips/syscall_nr.h
- linux-user/mips64/syscall_nr.h
- linux-user/sh4/syscall_nr.h
- linux-user/x86_64/syscall_nr.h
- linux-user/xtensa/syscall_nr.h
----------------------------------------------------------------------
Aleksandar Markovic (9):
linux-user: alpha: Update syscall numbers to kernel 5.5 level
linux-user: arm: Update syscall numbers to kernel 5.5 level
linux-user: m68k: Update syscall numbers to kernel 5.5 level
linux-user: microblaze: Update syscall numbers to kernel 5.5 level
linux-user: mips: Update syscall numbers to kernel 5.5 level
linux-user: sh4: Update syscall numbers to kernel 5.5 level
linux-user: x86_64: Update syscall numbers to kernel 5.5 level
linux-user: xtensa: Update syscall numbers to kernel 5.5 level
linux-user: xtensa: Remove unused constant TARGET_NR_syscall_count
linux-user/alpha/syscall_nr.h | 35 ++++++++++++++++
linux-user/arm/syscall_nr.h | 44 ++++++++++++++++++++
linux-user/m68k/syscall_nr.h | 50 ++++++++++++++++++++++-
linux-user/microblaze/syscall_nr.h | 45 +++++++++++++++++++++
linux-user/mips/syscall_nr.h | 45 +++++++++++++++++++++
linux-user/mips64/syscall_nr.h | 50 ++++++++++++++++++++++-
linux-user/sh4/syscall_nr.h | 48 ++++++++++++++++++++++
linux-user/x86_64/syscall_nr.h | 24 +++++++++++
linux-user/xtensa/syscall_nr.h | 36 ++++++++++++++++-
linux-user/mips/cpu_loop.c | 83 +++++++++++++++++++++++++++++++++++++-
10 files changed, 454 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2020-02-13 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 1:46 Aleksandar Markovic [this message]
2020-02-13 1:46 ` [PATCH v2 1/9] linux-user: alpha: Update syscall numbers to kernel 5.5 level Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 2/9] linux-user: arm: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 3/9] linux-user: m68k: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 4/9] linux-user: microblaze: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 5/9] linux-user: mips: " Aleksandar Markovic
2020-02-13 11:09 ` Laurent Vivier
2020-02-13 12:27 ` Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 6/9] linux-user: sh4: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 7/9] linux-user: x86_64: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 8/9] linux-user: xtensa: " Aleksandar Markovic
2020-02-13 1:46 ` [PATCH v2 9/9] linux-user: xtensa: Remove unused constant TARGET_NR_syscall_count Aleksandar Markovic
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=1581558393-9182-1-git-send-email-aleksandar.markovic@rt-rk.com \
--to=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--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;
as well as URLs for NNTP newsgroup(s).