linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: firoz.khan@linaro.org
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Greg KH <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>,
	Arnd Bergmann <arnd@arndb.de>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	marcin.juszkiewicz@linaro.org
Subject: Re: [PATCH v4 0/4] m68k: system call table generation support
Date: Sat, 27 Oct 2018 16:47:20 +0200	[thread overview]
Message-ID: <CAMuHMdXPR7WgPe5nPh3Lcc6FDxTNDYyOmV1oKU=BLcS2H7MPgA@mail.gmail.com> (raw)
In-Reply-To: <1540530377-3509-1-git-send-email-firoz.khan@linaro.org>

Hi Firoz,

On Fri, Oct 26, 2018 at 7:06 AM Firoz Khan <firoz.khan@linaro.org> wrote:
> The purpose of this patch series is, we can easily add/modify/delete
> system call table support by changing 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.
>
> The system call tables are in different format in all architecture.
> It will be difficult to manually add, modify or delete the system
> calls in the respective files manually. To make it easy by keeping
> a script and which'll generate uapi header file and syscall table
> file.
>
> syscall.tbl contains the list of available system calls along with
> system call number and corresponding entry point. Add a new system
> call in this architecture will be possible by adding new entry in
> the syscall.tbl file.
>
> Adding a new table entry consisting of:
>         - System call number.
>         - ABI.
>         - System call name.
>         - Entry point name.
>
> ARM, s390 and x86 architecuture does exist the similar support. I
> leverage their implementation to come up with a generic solution.
>
> I have done the same support for work for alpha, ia64, microblaze,
> mips, parisc, powerpc, sh, sparc, and xtensa. Below mentioned git
> repository contains more details.
> Git repo:- https://github.com/frzkhn/system_call_table_generator/
>
> Finally, this is the ground work to solve the Y2038 issue. We need
> to add two dozen of system calls to solve Y2038 issue. So this patch
> series will help to add new system calls easily by adding new entry
> in the syscall.tbl.

Thanks for the update!

Can you please tell the audience what has been changed in v4?

When posting a new version of a patch or patch series, it is a good
idea to include a changelog in the cover letter and/or patches.

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2018-10-27 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26  5:06 [PATCH v4 0/4] m68k: system call table generation support Firoz Khan
2018-10-26  5:06 ` Firoz Khan
2018-10-26  5:06 ` [PATCH v4 1/4] m68k: rename system call table file name Firoz Khan
2018-10-26  5:06   ` Firoz Khan
2018-10-26  5:06 ` [PATCH v4 2/4] m68k: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-10-26  5:06   ` Firoz Khan
2018-10-26  5:06 ` [PATCH v4 3/4] m68k: add system call table generation support Firoz Khan
2018-10-26  5:06   ` Firoz Khan
2018-10-26  5:06 ` [PATCH v4 4/4] m68k: generate uapi header and syscall table header files Firoz Khan
2018-10-26  5:06   ` Firoz Khan
2018-10-27 14:47 ` Geert Uytterhoeven [this message]
2018-10-27 14:47   ` [PATCH v4 0/4] m68k: system call table generation support Geert Uytterhoeven
2018-10-29  3:38   ` Firoz Khan
2018-10-29  3:38     ` 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='CAMuHMdXPR7WgPe5nPh3Lcc6FDxTNDYyOmV1oKU=BLcS2H7MPgA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --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=linux-m68k@lists.linux-m68k.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=pombredanne@nexb.com \
    --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).