From: David Miller <davem@davemloft.net>
To: firoz.khan@linaro.org
Cc: sparclinux@vger.kernel.org, geert@linux-m68k.org,
gregkh@linuxfoundation.org, pombredanne@nexb.com,
tglx@linutronix.de, kstewart@linuxfoundation.org,
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
Subject: Re: [PATCH v3 0/4] sparc: system call table generation support
Date: Sun, 18 Nov 2018 18:59:13 -0800 (PST) [thread overview]
Message-ID: <20181118.185913.65989390344960294.davem@davemloft.net> (raw)
In-Reply-To: <1542173191-24981-1-git-send-email-firoz.khan@linaro.org>
From: Firoz Khan <firoz.khan@linaro.org>
Date: Wed, 14 Nov 2018 10:56:27 +0530
> The purpose of this patch series is, we can easily
> add/modify/delete system call table support by cha-
> nging entry in syscall.tbl file instead of manually
> changing many files. The other goal is to unify the
> system call table generation support implementation
> across all the architectures.
...
Series applied to sparc-next.
next prev parent reply other threads:[~2018-11-19 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 5:26 [PATCH v3 0/4] sparc: system call table generation support Firoz Khan
2018-11-14 5:26 ` [PATCH v3 1/4] sparc: move __IGNORE* entries to non uapi header Firoz Khan
2018-11-14 5:26 ` [PATCH v3 2/4] sparc: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-14 5:26 ` [PATCH v3 3/4] sparc: add system call table generation support Firoz Khan
2018-11-14 5:26 ` [PATCH v3 4/4] sparc: generate uapi header and system call table files Firoz Khan
2018-11-14 6:44 ` [PATCH v3 0/4] sparc: system call table generation support Allen
2018-11-14 7:04 ` Firoz Khan
2018-11-19 2:59 ` David Miller [this message]
2018-11-19 5:22 ` 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=20181118.185913.65989390344960294.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=geert@linux-m68k.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).