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 4/4] linux-user: remove _sysctl
Date: Wed, 30 Sep 2020 02:30:33 +0200 [thread overview]
Message-ID: <20200930003033.554124-5-laurent@vivier.eu> (raw)
In-Reply-To: <20200930003033.554124-1-laurent@vivier.eu>
It has been removed from linux since
61a47c1ad3a4 ("sysctl: Remove the sysctl system call")
It's a good news because it was not really supported by qemu.
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
linux-user/syscall.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 897d20c076ce..0cfc95088fa4 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -10524,12 +10524,6 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
#if defined(TARGET_NR_fdatasync) /* Not on alpha (osf_datasync ?) */
case TARGET_NR_fdatasync:
return get_errno(fdatasync(arg1));
-#endif
-#ifdef TARGET_NR__sysctl
- case TARGET_NR__sysctl:
- /* We don't implement this, but ENOTDIR is always a safe
- return value. */
- return -TARGET_ENOTDIR;
#endif
case TARGET_NR_sched_getaffinity:
{
--
2.26.2
next prev parent reply other threads:[~2020-09-30 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 0:30 [PATCH 0/4] linux-user: update syscall_nr headers to Linux 5.9-rc7 Laurent Vivier
2020-09-30 0:30 ` [PATCH 1/4] linux-user: update syscall_nr.h " 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 ` Laurent Vivier [this message]
2020-10-02 17:20 ` [PATCH 0/4] linux-user: update syscall_nr headers " 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-5-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).