From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Rashmica Gupta <rashmicy@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Standardise on NR_syscalls rather than __NR_syscalls.
Date: Mon, 23 Nov 2015 11:53:10 +0530 [thread overview]
Message-ID: <5652B0CE.40704@linux.vnet.ibm.com> (raw)
In-Reply-To: <1447913093-28342-1-git-send-email-rashmicy@gmail.com>
On 11/19/2015 11:34 AM, Rashmica Gupta wrote:
> Most architectures use NR_syscalls as the #define for the number of syscalls.
>
> We use __NR_syscalls, and then define NR_syscalls as __NR_syscalls.
>
> __NR_syscalls is not used outside arch code, whereas NR_syscalls is. So as
> NR_syscalls must be defined and __NR_syscalls does not, replace __NR_syscalls
> with NR_syscalls.
>
> Signed-off-by: Rashmica Gupta <rashmicy@gmail.com>
> ---
> arch/powerpc/include/asm/unistd.h | 3 +--
> arch/powerpc/include/asm/vdso_datapage.h | 2 +-
> arch/powerpc/kernel/systbl_chk.c | 2 +-
> arch/powerpc/kernel/systbl_chk.sh | 2 +-
> arch/powerpc/kernel/vdso.c | 2 +-
> arch/powerpc/kernel/vdso32/datapage.S | 2 +-
> arch/powerpc/kernel/vdso64/datapage.S | 2 +-
> arch/powerpc/platforms/cell/spufs/run.c | 2 +-
> 8 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/unistd.h b/arch/powerpc/include/asm/unistd.h
> index 6d8f8023ac27..05bf34296144 100644
> --- a/arch/powerpc/include/asm/unistd.h
> +++ b/arch/powerpc/include/asm/unistd.h
> @@ -12,10 +12,9 @@
> #include <uapi/asm/unistd.h>
>
>
> -#define __NR_syscalls 378
> +#define NR_syscalls 378
This does not apply any more because of Michael's recent mlock2() system
call enablement commit. Please do rebase and resend.
- Anshuman
next prev parent reply other threads:[~2015-11-23 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 6:04 [PATCH] powerpc: Standardise on NR_syscalls rather than __NR_syscalls Rashmica Gupta
2015-11-19 9:15 ` Denis Kirjanov
2015-11-19 9:59 ` Anshuman Khandual
2015-11-19 10:33 ` Benjamin Herrenschmidt
2015-11-23 3:29 ` Michael Ellerman
2015-11-23 9:28 ` Denis Kirjanov
2015-11-23 10:14 ` Michael Ellerman
2015-11-23 6:23 ` Anshuman Khandual [this message]
2015-11-23 23:22 ` Michael Ellerman
2015-11-26 12:15 ` Michael Ellerman
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=5652B0CE.40704@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rashmicy@gmail.com \
/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).