From: Al Viro <viro@ZenIV.linux.org.uk>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: linux-arch@vger.kernel.org, arnd@arndb.de,
y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
ink@jurassic.park.msu.ru, deepa.kernel@gmail.com,
linux-alpha@vger.kernel.org, mattst88@gmail.com, rth@twiddle.net
Subject: Re: [PATCH 1/6] alpha: Move __IGNORE* entries to non uapi header
Date: Sat, 11 Aug 2018 20:28:04 +0100 [thread overview]
Message-ID: <20180811192804.GI6515@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1531736638-15294-2-git-send-email-firoz.khan@linaro.org>
On Mon, Jul 16, 2018 at 03:53:53PM +0530, Firoz Khan wrote:
> 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.
> diff --git a/arch/alpha/include/uapi/asm/unistd.h b/arch/alpha/include/uapi/asm/unistd.h
> index e153ca6..3bb6ac1 100644
> --- a/arch/alpha/include/uapi/asm/unistd.h
> +++ b/arch/alpha/include/uapi/asm/unistd.h
> @@ -481,9 +481,4 @@
> #define __NR_pwritev2 521
> #define __NR_statx 522
>
> -/* Alpha doesn't have protection keys. */
> -#define __IGNORE_pkey_mprotect
> -#define __IGNORE_pkey_alloc
> -#define __IGNORE_pkey_free
> -
> #endif /* _UAPI_ALPHA_UNISTD_H */
Hmm... There's also
#define __IGNORE_alarm
#define __IGNORE_creat
#define __IGNORE_getegid
#define __IGNORE_geteuid
#define __IGNORE_getgid
#define __IGNORE_getpid
#define __IGNORE_getppid
#define __IGNORE_getuid
#define __IGNORE_pause
#define __IGNORE_time
#define __IGNORE_utime
#define __IGNORE_umount2
in there...
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: linux-alpha@vger.kernel.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, arnd@arndb.de,
deepa.kernel@gmail.com
Subject: Re: [PATCH 1/6] alpha: Move __IGNORE* entries to non uapi header
Date: Sat, 11 Aug 2018 20:28:04 +0100 [thread overview]
Message-ID: <20180811192804.GI6515@ZenIV.linux.org.uk> (raw)
Message-ID: <20180811192804.8sRTr2G9qwDZawQLRIaNXThv-y6lI7Zo1E559UiHQM4@z> (raw)
In-Reply-To: <1531736638-15294-2-git-send-email-firoz.khan@linaro.org>
On Mon, Jul 16, 2018 at 03:53:53PM +0530, Firoz Khan wrote:
> 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.
> diff --git a/arch/alpha/include/uapi/asm/unistd.h b/arch/alpha/include/uapi/asm/unistd.h
> index e153ca6..3bb6ac1 100644
> --- a/arch/alpha/include/uapi/asm/unistd.h
> +++ b/arch/alpha/include/uapi/asm/unistd.h
> @@ -481,9 +481,4 @@
> #define __NR_pwritev2 521
> #define __NR_statx 522
>
> -/* Alpha doesn't have protection keys. */
> -#define __IGNORE_pkey_mprotect
> -#define __IGNORE_pkey_alloc
> -#define __IGNORE_pkey_free
> -
> #endif /* _UAPI_ALPHA_UNISTD_H */
Hmm... There's also
#define __IGNORE_alarm
#define __IGNORE_creat
#define __IGNORE_getegid
#define __IGNORE_geteuid
#define __IGNORE_getgid
#define __IGNORE_getpid
#define __IGNORE_getppid
#define __IGNORE_getuid
#define __IGNORE_pause
#define __IGNORE_time
#define __IGNORE_utime
#define __IGNORE_umount2
in there...
next prev parent reply other threads:[~2018-08-11 19:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 10:23 [PATCH 0/6] System call table generation support Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-07-16 10:23 ` [PATCH 1/6] alpha: Move __IGNORE* entries to non uapi header Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-08-11 19:28 ` Al Viro [this message]
2018-08-11 19:28 ` Al Viro
2018-08-11 20:59 ` Michael Cree
2018-08-11 20:59 ` Michael Cree
2018-08-11 22:27 ` Arnd Bergmann
2018-08-11 22:27 ` Arnd Bergmann
2018-07-16 10:23 ` [PATCH 2/6] alpha: Add CONFIG_OSF4_COMPAT for compat syscall support Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-07-16 10:23 ` [PATCH 3/6] alpha: Unify the not-implemented system call entry name Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-08-11 0:04 ` Al Viro
2018-08-11 0:04 ` Al Viro
2018-08-11 2:31 ` Richard Henderson
2018-08-11 2:31 ` Richard Henderson
2018-08-11 2:45 ` Al Viro
2018-08-11 2:45 ` Al Viro
2018-08-11 4:10 ` Richard Henderson
2018-08-11 4:10 ` Richard Henderson
2018-08-11 15:07 ` Al Viro
2018-08-11 15:07 ` Al Viro
2018-08-11 15:24 ` Richard Henderson
2018-08-11 15:24 ` Richard Henderson
2018-07-16 10:23 ` [PATCH 4/6] alpha: Replace NR_SYSCALLS macro from asm/unistd.h Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-07-16 10:23 ` [PATCH 5/6] alpha: Add system call table generation support Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-07-16 10:23 ` [PATCH 6/6] alpha: uapi header and system call table file generation Firoz Khan
2018-07-16 10:23 ` Firoz Khan
2018-07-16 16:23 ` kbuild test robot
2018-07-16 16:23 ` kbuild test robot
2018-07-16 14:09 ` [PATCH 0/6] System call table generation support Arnd Bergmann
2018-07-16 14:09 ` Arnd Bergmann
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=20180811192804.GI6515@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--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).