From: Philippe De Muyter <phdm@macq.eu>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <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 v2 1/5] m68k: Rename system call table file name
Date: Fri, 21 Sep 2018 07:48:51 +0200 [thread overview]
Message-ID: <20180921054850.GA13343@frolo.macqel> (raw)
Message-ID: <20180921054851.KW4DkVE6K6k7h4JhxX1W0g04j48GnfYRfpU4NLtw6cE@z> (raw)
In-Reply-To: <1537455973-12468-2-git-send-email-firoz.khan@linaro.org>
On Thu, Sep 20, 2018 at 08:36:09PM +0530, Firoz Khan wrote:
> The system call table entries are present in syscalltable.S. One of
> the patch in this patch series will auto-generate the system call
> table entries using the system call table generation script and
> which'll replace the existig table file.
>
> In order to come up with a common naming convention across all
> architecture, we need to change the file name to syscall_table.S.
That file was probably called that way to be able to distinguish it
from syscalltable.s and syscalltable.o in a file system with a 14
characters limit in file names (in sysV unix systems).
> This change will unify the implementation across all architecture.
>
> Signed-off-by: Firoz Khan <firoz.khan@linaro.org>
> ---
> arch/m68k/kernel/Makefile | 2 +-
> arch/m68k/kernel/syscall_table.S | 403 +++++++++++++++++++++++++++++++++++++++
> arch/m68k/kernel/syscalltable.S | 403 ---------------------------------------
You should generate your patch with the '-M' or '--find-renames' option.
Philippe
--
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
next prev parent reply other threads:[~2018-09-21 11:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 15:06 [PATCH v2 0/5] System call table generation support Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-20 15:06 ` [PATCH v2 1/5] m68k: Rename system call table file name Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-21 5:48 ` Philippe De Muyter [this message]
2018-09-21 5:48 ` Philippe De Muyter
2018-09-22 11:36 ` Firoz Khan
2018-09-22 11:36 ` Firoz Khan
2018-09-24 7:00 ` Geert Uytterhoeven
2018-09-24 7:00 ` Geert Uytterhoeven
2018-09-20 15:06 ` [PATCH v2 2/5] m68k: Replace NR_syscalls macro from asm/unistd.h Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-24 7:01 ` Geert Uytterhoeven
2018-09-24 7:01 ` Geert Uytterhoeven
2018-09-24 7:02 ` Geert Uytterhoeven
2018-09-24 7:02 ` Geert Uytterhoeven
2018-09-20 15:06 ` [PATCH v2 3/5] m68k: Added system call table generation support Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-24 7:03 ` Geert Uytterhoeven
2018-09-24 7:03 ` Geert Uytterhoeven
2018-09-24 7:53 ` Firoz Khan
2018-09-24 7:53 ` Firoz Khan
2018-09-20 15:06 ` [PATCH v2 4/5] m68k: uapi header and system call table file generation Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-24 7:05 ` Geert Uytterhoeven
2018-09-24 7:05 ` Geert Uytterhoeven
2018-09-24 7:55 ` Firoz Khan
2018-09-24 7:55 ` Firoz Khan
2018-09-20 15:06 ` [PATCH v2 5/5] m68k: added __IGNORE* entries in asm/unistd.h Firoz Khan
2018-09-20 15:06 ` Firoz Khan
2018-09-24 7:05 ` Geert Uytterhoeven
2018-09-24 7:05 ` Geert Uytterhoeven
2018-09-24 1:08 ` [PATCH v2 0/5] System call table generation support Greg Ungerer
2018-09-24 1:08 ` Greg Ungerer
2018-09-24 4:08 ` Firoz Khan
2018-09-24 4:08 ` Firoz Khan
2018-09-24 7:06 ` Geert Uytterhoeven
2018-09-24 7:06 ` Geert Uytterhoeven
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=20180921054850.GA13343@frolo.macqel \
--to=phdm@macq.eu \
--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=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).