From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Firoz Khan <firoz.khan@linaro•org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Al Viro <viro@zeniv•linux.org.uk>,
linuxppc-dev@lists•ozlabs.org,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Philippe Ombredanne <pombredanne@nexb•com>,
Thomas Gleixner <tglx@linutronix•de>,
Kate Stewart <kstewart@linuxfoundation•org>
Cc: linux-arch@vger•kernel.org, arnd@arndb•de,
y2038@lists•linaro.org, linux-kernel@vger•kernel.org,
marcin.juszkiewicz@linaro•org, firoz.khan@linaro•org,
deepa.kernel@gmail•com
Subject: Re: [1/2] powerpc: remove nargs from __SYSCALL
Date: Mon, 4 Mar 2019 11:48:06 +1100 (AEDT) [thread overview]
Message-ID: <44CLwk4pdDz9s6w@ozlabs.org> (raw)
In-Reply-To: <1546441324-19774-2-git-send-email-firoz.khan@linaro.org>
On Wed, 2019-01-02 at 15:02:03 UTC, Firoz Khan wrote:
> The __SYSCALL macro's arguments are system call number,
> system call entry name and number of arguments for the
> system call.
>
> Argument- nargs in __SYSCALL(nr, entry, nargs) is neither
> calculated nor used anywhere. So it would be better to
> keep the implementaion as __SYSCALL(nr, entry). This will
> unifies the implementation with some other architetures
> too.
>
> Signed-off-by: Firoz Khan <firoz.khan@linaro•org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/6b1200facc051a3e487a52cbabd745f7
cheers
next prev parent reply other threads:[~2019-03-04 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 15:02 [PATCH 0/2] powerpc: Unify the system call scripts Firoz Khan
2019-01-02 15:02 ` [PATCH 1/2] powerpc: remove nargs from __SYSCALL Firoz Khan
2019-03-04 0:48 ` Michael Ellerman [this message]
2019-01-02 15:02 ` [PATCH 2/2] powerpc: generate uapi header and system call table files 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=44CLwk4pdDz9s6w@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=deepa.kernel@gmail$(echo .)com \
--cc=firoz.khan@linaro$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=kstewart@linuxfoundation$(echo .)org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=marcin.juszkiewicz@linaro$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=pombredanne@nexb$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=y2038@lists$(echo .)linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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