From: Arnd Bergmann <arnd@arndb.de>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: David Miller <davem@davemloft.net>,
sparclinux <sparclinux@vger.kernel.org>,
gregkh <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH 4/4] sparc: uapi header and system call table file generation
Date: Thu, 6 Sep 2018 17:34:11 +0200 [thread overview]
Message-ID: <CAK8P3a2qFoCOzM6x-_mv0Um2E-WHDeOU-fuuZ65TtDKKcPxNrQ@mail.gmail.com> (raw)
In-Reply-To: <1536036087-15260-5-git-send-email-firoz.khan@linaro.org>
On Tue, Sep 4, 2018 at 6:42 AM Firoz Khan <firoz.khan@linaro.org> wrote:
>
> System call table generation script must be run to generate
> unistd_32/64.h and syscall_table_32/64/c32.h files. This patch
> will have changes which will invokes the script.
>
> This patch will generate unistd_32/64.h and syscall_table_
> 32/64/c32.h files by the syscall table generation script
> invoked by arch/sparc/Makefile and the generated files against
> the removed files will be identical.
>
> The generated uapi header file will be included in uapi/asm/
> unistd_32/64.h and generated system call table support file will
> be included by arch/sparc/kernel/syscall_table_32/64.S file.
These changes all look good to me.
Arnd
next prev parent reply other threads:[~2018-09-06 15:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 4:41 [PATCH 0/4] System call table generation support Firoz Khan
2018-09-04 4:41 ` Firoz Khan
2018-09-04 4:41 ` [PATCH 1/4] sparc: Move __IGNORE* entries to non uapi header Firoz Khan
2018-09-04 4:41 ` Firoz Khan
2018-09-06 15:28 ` Arnd Bergmann
2018-09-06 15:28 ` Arnd Bergmann
2018-09-18 11:53 ` Firoz Khan
2018-09-18 11:53 ` Firoz Khan
2018-09-24 21:06 ` Arnd Bergmann
2018-09-24 21:06 ` Arnd Bergmann
2018-09-06 19:09 ` kbuild test robot
2018-09-06 19:09 ` kbuild test robot
2018-09-04 4:41 ` [PATCH 2/4] sparc: Replace NR_SYSCALLS macro with __NR_SYSCALLS Firoz Khan
2018-09-04 4:41 ` Firoz Khan
2018-09-06 15:29 ` Arnd Bergmann
2018-09-06 15:29 ` Arnd Bergmann
2018-09-18 9:45 ` Firoz Khan
2018-09-18 9:45 ` Firoz Khan
2018-09-04 4:41 ` [PATCH 3/4] sparc: Add system call table generation support Firoz Khan
2018-09-04 4:41 ` Firoz Khan
2018-09-06 15:32 ` Arnd Bergmann
2018-09-06 15:32 ` Arnd Bergmann
2018-09-18 11:37 ` Firoz Khan
2018-09-18 11:37 ` Firoz Khan
2018-09-04 4:41 ` [PATCH 4/4] sparc: uapi header and system call table file generation Firoz Khan
2018-09-04 4:41 ` Firoz Khan
2018-09-06 15:34 ` Arnd Bergmann [this message]
2018-09-06 15:34 ` Arnd Bergmann
2018-09-18 11:45 ` Firoz Khan
2018-09-18 11:45 ` Firoz Khan
2018-09-06 21:12 ` kbuild test robot
2018-09-06 21:12 ` kbuild test robot
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=CAK8P3a2qFoCOzM6x-_mv0Um2E-WHDeOU-fuuZ65TtDKKcPxNrQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=sparclinux@vger.kernel.org \
--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).