qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
	Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Laurent Vivier <laurent@vivier.eu>
Subject: [PATCH 0/4] linux-user: update syscall_nr headers to Linux 5.9-rc7
Date: Wed, 30 Sep 2020 02:30:29 +0200	[thread overview]
Message-ID: <20200930003033.554124-1-laurent@vivier.eu> (raw)

All the changes have been done using:

scripts/gensyscalls.sh, scripts/update-mips-syscall-args.sh and
scripts/update-syscalltbl.sh

I've checked syscall_nr.h generated from syscall.tbl are
always correctly generated (there have been massive changes in
x86 targets).

The series also removes _sysctl from syscall.c as it has been
removed from the kernel (and we didn't emulate it correctly)

Laurent Vivier (4):
  linux-user: update syscall_nr.h to Linux 5.9-rc7
  linux-user: update mips/syscall-args-o32.c.inc to Linux 5.9-rc7
  linux-user: update syscall.tbl to Linux 5.9-rc7
  linux-user: remove _sysctl

 linux-user/aarch64/syscall_nr.h        |   7 +-
 linux-user/alpha/syscall.tbl           |   4 +-
 linux-user/arm/syscall.tbl             |   4 +-
 linux-user/hppa/syscall.tbl            |   8 +-
 linux-user/i386/syscall_32.tbl         | 820 +++++++++++++------------
 linux-user/m68k/syscall.tbl            |   4 +-
 linux-user/microblaze/syscall.tbl      |   4 +-
 linux-user/mips/syscall-args-o32.c.inc |   4 +
 linux-user/mips/syscall_o32.tbl        |   8 +-
 linux-user/mips64/syscall_n32.tbl      |   8 +-
 linux-user/mips64/syscall_n64.tbl      |   4 +-
 linux-user/nios2/syscall_nr.h          |   7 +-
 linux-user/openrisc/syscall_nr.h       |   8 +-
 linux-user/ppc/syscall.tbl             |  30 +-
 linux-user/riscv/syscall32_nr.h        |   8 +-
 linux-user/riscv/syscall64_nr.h        |   8 +-
 linux-user/s390x/syscall.tbl           |   8 +-
 linux-user/sh4/syscall.tbl             |   4 +-
 linux-user/sparc/syscall.tbl           |   8 +-
 linux-user/sparc64/syscall.tbl         |   8 +-
 linux-user/syscall.c                   |   6 -
 linux-user/x86_64/syscall_64.tbl       | 742 +++++++++++-----------
 linux-user/xtensa/syscall.tbl          |   4 +-
 scripts/gensyscalls.sh                 |   3 +-
 24 files changed, 889 insertions(+), 830 deletions(-)

-- 
2.26.2



             reply	other threads:[~2020-09-30  0:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  0:30 Laurent Vivier [this message]
2020-09-30  0:30 ` [PATCH 1/4] linux-user: update syscall_nr.h to Linux 5.9-rc7 Laurent Vivier
2020-09-30  1:12   ` Alistair Francis
2020-09-30  0:30 ` [PATCH 2/4] linux-user: update mips/syscall-args-o32.c.inc " Laurent Vivier
2020-10-09 15:22   ` Philippe Mathieu-Daudé
2020-09-30  0:30 ` [PATCH 3/4] linux-user: update syscall.tbl " Laurent Vivier
2020-09-30  0:30 ` [PATCH 4/4] linux-user: remove _sysctl Laurent Vivier
2020-10-02 17:20 ` [PATCH 0/4] linux-user: update syscall_nr headers to Linux 5.9-rc7 Richard Henderson
2020-10-26 10:40 ` 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=20200930003033.554124-1-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=aleksandar.qemu.devel@gmail.com \
    --cc=aleksandar.rikalo@syrmia.com \
    --cc=aurelien@aurel32.net \
    --cc=jiaxun.yang@flygoat.com \
    --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).