From: Firoz Khan <firoz.khan@linaro.org>
To: linux-ia64@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, arnd@arndb.de,
deepa.kernel@gmail.com, marcin.juszkiewicz@linaro.org,
firoz.khan@linaro.org
Subject: [PATCH v2 7/7] ia64: add __IGNORE* entries in asm/unistd.h
Date: Thu, 27 Sep 2018 19:45:20 +0530 [thread overview]
Message-ID: <1538057720-3392-8-git-send-email-firoz.khan@linaro.org> (raw)
In-Reply-To: <1538057720-3392-1-git-send-email-firoz.khan@linaro.org>
Add __IGNORE* entries for perf_event_open, seccomp, pkey_
mprotect, pkey_alloc, pkey_free, statx, io_pgetevents and
rseq in the file asm/unistd.h as it is correct to keep
__IGNORE* entry in non uapi header asm/unistd.h while uapi/
asm/unistd.h must hold information only useful for user
space applications.
Signed-off-by: Firoz Khan <firoz.khan@linaro.org>
---
arch/ia64/include/asm/unistd.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/ia64/include/asm/unistd.h b/arch/ia64/include/asm/unistd.h
index 397b143..a0941e6 100644
--- a/arch/ia64/include/asm/unistd.h
+++ b/arch/ia64/include/asm/unistd.h
@@ -26,6 +26,15 @@
#define __IGNORE_vfork /* clone() */
#define __IGNORE_umount2 /* umount() */
+#define __IGNORE_perf_event_open
+#define __IGNORE_seccomp
+#define __IGNORE_pkey_mprotect
+#define __IGNORE_pkey_alloc
+#define __IGNORE_pkey_free
+#define __IGNORE_statx
+#define __IGNORE_io_pgetevents
+#define __IGNORE_rseq
+
#if !defined(__ASSEMBLY__) && !defined(ASSEMBLER)
#include <linux/types.h>
--
1.9.1
next prev parent reply other threads:[~2018-09-27 14:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:15 [PATCH v2 0/7] System call table generation support Firoz Khan
2018-09-27 14:15 ` [PATCH v2 1/7] ia64: add __NR_old_getpagesize macro Firoz Khan
2018-09-28 12:11 ` Arnd Bergmann
2018-10-01 14:18 ` Firoz Khan
2018-10-01 14:44 ` Arnd Bergmann
2018-09-27 14:15 ` [PATCH v2 2/7] ia64: replace NR_syscalls macro from asm/unistd.h Firoz Khan
2018-09-27 14:15 ` [PATCH v2 3/7] ia64: add an offset for system call number Firoz Khan
2018-09-27 14:15 ` [PATCH v2 4/7] ia64: replace the system call table entries from entry.S Firoz Khan
2018-09-27 14:15 ` [PATCH v2 5/7] ia64: add system call table generation support Firoz Khan
2018-09-27 14:15 ` [PATCH v2 6/7] ia64: uapi header and system call table file generation Firoz Khan
2018-09-28 12:10 ` Arnd Bergmann
2018-10-01 14:15 ` Firoz Khan
2018-09-27 14:15 ` Firoz Khan [this message]
2018-09-28 12:09 ` [PATCH v2 7/7] ia64: add __IGNORE* entries in asm/unistd.h Arnd Bergmann
2018-09-28 17:30 ` [PATCH v2 0/7] System call table generation support Luck, Tony
2018-10-01 14:21 ` Firoz Khan
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=1538057720-3392-8-git-send-email-firoz.khan@linaro.org \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=y2038@lists.linaro.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).