From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f180.google.com ([209.85.216.180]:41983 "EHLO mail-qt0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730122AbeIFUJQ (ORCPT ); Thu, 6 Sep 2018 16:09:16 -0400 MIME-Version: 1.0 References: <1536036087-15260-1-git-send-email-firoz.khan@linaro.org> <1536036087-15260-4-git-send-email-firoz.khan@linaro.org> In-Reply-To: <1536036087-15260-4-git-send-email-firoz.khan@linaro.org> From: Arnd Bergmann Date: Thu, 6 Sep 2018 17:32:56 +0200 Message-ID: Subject: Re: [PATCH 3/4] sparc: Add system call table generation support Content-Type: text/plain; charset="UTF-8" Sender: linux-arch-owner@vger.kernel.org List-ID: To: Firoz Khan Cc: David Miller , sparclinux , gregkh , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , y2038 Mailman List , Linux Kernel Mailing List , linux-arch , Deepa Dinamani , Marcin Juszkiewicz Message-ID: <20180906153256.w0SRrAosVvCY_i5A9Ox3Hby_Knvrpfskq8nV3CWEEK0@z> On Tue, Sep 4, 2018 at 6:42 AM Firoz Khan wrote: > The system call table generation script is added in > syscalls directory which contain the script to generate > both uapi header file system call table generation file > and syscall_32/64.tbl file which'll be the input for the > scripts. I would argue that for sparc we only want a single input table, since the 32/64 versions are similar enough that the differences can be addressed with 'abi' flag, rather than having everything marked as 'common'. Isn't that the purpose of the abi flag in the first place? Arnd