From: Arnd Bergmann <arnd@arndb.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Firoz Khan <firoz.khan@linaro.org>
Subject: Re: [RFC PATCH 1/5] powerpc/syscalls: Remove unused offset parameter
Date: Tue, 15 Jan 2019 17:27:48 +0100 [thread overview]
Message-ID: <CAK8P3a3PnbJ1Mr01HeRUzk+cfK4t-yok4YTJdNrBs6f==fVrnw@mail.gmail.com> (raw)
In-Reply-To: <20190114113620.17558-1-mpe@ellerman.id.au>
On Mon, Jan 14, 2019 at 12:36 PM Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> We never pass a value for offset, nor do we need to, so remove the
> offset logic.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
This change and the next three defeat the idea of having a shared script across
all architectures. Firoz has already posted patches to move the scripts to
scripts/syscalltbl.sh, and I think it's better to go on with those
patches, as they
also guarantee that the format of the files remains consistent across all
architectures.
Arnd
next prev parent reply other threads:[~2019-01-15 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 11:36 [RFC PATCH 1/5] powerpc/syscalls: Remove unused offset parameter Michael Ellerman
2019-01-14 11:36 ` [RFC PATCH 2/5] powerpc/syscalls: Remove unused prefix parameter Michael Ellerman
2019-01-16 2:44 ` Firoz Khan
2019-01-14 11:36 ` [RFC PATCH 3/5] powerpc/syscalls: Split SPU-ness out of ABI Michael Ellerman
2019-01-15 16:30 ` Arnd Bergmann
2019-01-14 11:36 ` [RFC PATCH 4/5] powerpc/syscalls: Allow none instead of sys_ni_syscall Michael Ellerman
2019-01-18 6:23 ` Firoz Khan
2019-01-14 11:36 ` [RFC PATCH 5/5] powerpc/syscalls: Use the number when building SPU syscall table Michael Ellerman
2019-01-15 16:26 ` Arnd Bergmann
2019-01-15 16:27 ` Arnd Bergmann [this message]
2019-01-16 0:31 ` [RFC PATCH 1/5] powerpc/syscalls: Remove unused offset parameter Michael Ellerman
2019-01-16 10:19 ` Arnd Bergmann
2019-01-16 12:54 ` Michael Ellerman
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='CAK8P3a3PnbJ1Mr01HeRUzk+cfK4t-yok4YTJdNrBs6f==fVrnw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=firoz.khan@linaro.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).