From: Thomas Richter <tmricht@linux.vnet.ibm.com>
To: trinity@vger.kernel.org, davej@codemonkey.org.uk
Cc: brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com,
Thomas Richter <tmricht@linux.vnet.ibm.com>
Subject: [PATCH 7/7] trinity: Add support for readdir svc
Date: Tue, 6 Feb 2018 09:02:29 +0100 [thread overview]
Message-ID: <20180206080229.27721-7-tmricht@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180206080229.27721-1-tmricht@linux.vnet.ibm.com>
Add support for system call readdir on s390 (31 bit).
Signed-off-by: Thomas Richter <tmricht@linux.vnet.ibm.com>
---
include/syscalls-s390.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/syscalls-s390.h b/include/syscalls-s390.h
index 027a9fcd..682d2030 100644
--- a/include/syscalls-s390.h
+++ b/include/syscalls-s390.h
@@ -96,7 +96,7 @@ struct syscalltable syscalls_s390[] = {
{ .entry = &syscall_uselib },
{ .entry = &syscall_swapon },
{ .entry = &syscall_reboot },
- { .entry = &syscall_ni_syscall }, /* TODO: readdir systemcall */
+ { .entry = &syscall_oldreaddir },
{ .entry = &syscall_mmap }, /* old_mmap */
{ .entry = &syscall_munmap },
{ .entry = &syscall_truncate },
--
2.14.3
prev parent reply other threads:[~2018-02-06 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 8:02 [PATCH 1/7] trinity: Fix compile error on linux 4.15 kernel Thomas Richter
2018-02-06 8:02 ` [PATCH 2/7] trinity: Update and comment on s390 system call table Thomas Richter
2018-02-06 8:02 ` [PATCH 3/7] trinity: Add support for preadv2/pwritev2 svcs Thomas Richter
2018-02-06 8:02 ` [PATCH 4/7] trinity: Add support for statx svc Thomas Richter
2018-02-06 8:02 ` [PATCH 5/7] trinity: Add support for mlock2 svc Thomas Richter
2018-02-06 8:02 ` [PATCH 6/7] trinity: Add support for copy_file_range svc Thomas Richter
2018-02-06 8:02 ` Thomas Richter [this message]
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=20180206080229.27721-7-tmricht@linux.vnet.ibm.com \
--to=tmricht@linux.vnet.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=davej@codemonkey.org.uk \
--cc=heiko.carstens@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=trinity@vger.kernel.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).