[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181101.230427.364286844194487248.davem@davemloft.net>
Date: Thu, 01 Nov 2018 23:04:27 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: firoz.khan@...aro.org
Cc: sparclinux@...r.kernel.org, gregkh@...uxfoundation.org,
pombredanne@...b.com, tglx@...utronix.de,
kstewart@...uxfoundation.org, y2038@...ts.linaro.org,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
arnd@...db.de, deepa.kernel@...il.com,
marcin.juszkiewicz@...aro.org
Subject: Re: [PATCH v2 3/4] sparc: add system call table generation support
From: Firoz Khan <firoz.khan@...aro.org>
Date: Fri, 2 Nov 2018 11:09:57 +0530
> On Fri, 2 Nov 2018 at 02:03, David Miller <davem@...emloft.net> wrote:
>>
>> If sys_nis_syscall for the compat syscall shows up in a situation where the
>> native 32-bit syscall does have an entry, that's a BUG and the script should
>> point this out so that the bug can be fixed.
>
> syscall.tbl is the input to the script, so the developers has the
> responsibility to fill the table
> properly. I don't know, we have to write a script which has to be
> smart enough to catch the
> wrong syscall entries.
It does not need anything "smart", it just needs to see that
sys_nis_syscall in the "compat" column just as my eyes noticed
them in your patch.
It can be completely automated.
Powered by blists - more mailing lists