linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Firoz Khan <firoz.khan@linaro.org>
To: linux-parisc@vger.kernel.org,
	"James E . J . Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>,
	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 5/5] parisc: add __IGNORE* entries in asm/unistd.h
Date: Thu, 27 Sep 2018 19:54:27 +0530	[thread overview]
Message-ID: <1538058267-3765-6-git-send-email-firoz.khan@linaro.org> (raw)
In-Reply-To: <1538058267-3765-1-git-send-email-firoz.khan@linaro.org>

Add __IGNORE* entries for nfsservctl, 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/parisc/include/asm/unistd.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/parisc/include/asm/unistd.h b/arch/parisc/include/asm/unistd.h
index 93fd9f6..9294e10 100644
--- a/arch/parisc/include/asm/unistd.h
+++ b/arch/parisc/include/asm/unistd.h
@@ -13,6 +13,9 @@
 #define __IGNORE_pkey_mprotect
 #define __IGNORE_pkey_alloc
 #define __IGNORE_pkey_free
+#define __IGNORE_nfsservctl
+#define __IGNORE_io_pgetevents
+#define __IGNORE_rseq
 
 #ifndef ASM_LINE_SEP
 # define ASM_LINE_SEP ;
-- 
1.9.1

  parent reply	other threads:[~2018-09-27 14:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 14:24 [PATCH v2 0/5] System call table generation support Firoz Khan
2018-09-27 14:24 ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 1/5] parisc: move __IGNORE* entries to non uapi header Firoz Khan
2018-09-27 14:24   ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 2/5] parisc: add __NR_Linux_syscalls macro with __NR_syscalls Firoz Khan
2018-09-27 14:24   ` Firoz Khan
2018-09-28 12:14   ` Arnd Bergmann
2018-09-28 12:14     ` Arnd Bergmann
2018-10-01 14:06     ` Firoz Khan
2018-10-01 14:06       ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 3/5] parisc: add system call table generation support Firoz Khan
2018-09-27 14:24   ` Firoz Khan
2018-10-01 11:36   ` Arnd Bergmann
2018-10-01 11:36     ` Arnd Bergmann
2018-10-01 14:23     ` Firoz Khan
2018-10-01 14:23       ` Firoz Khan
2018-10-03  8:47   ` Firoz Khan
2018-10-03  8:47     ` Firoz Khan
2018-09-27 14:24 ` [PATCH v2 4/5] parisc: uapi header and system call table file generation Firoz Khan
2018-09-27 14:24   ` Firoz Khan
2018-09-27 14:24 ` Firoz Khan [this message]
2018-09-27 14:24   ` [PATCH v2 5/5] parisc: add __IGNORE* entries in asm/unistd.h 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=1538058267-3765-6-git-send-email-firoz.khan@linaro.org \
    --to=firoz.khan@linaro.org \
    --cc=arnd@arndb.de \
    --cc=deepa.kernel@gmail.com \
    --cc=deller@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jejb@parisc-linux.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --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).