Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1082715imu; Mon, 5 Nov 2018 13:33:39 -0800 (PST) X-Google-Smtp-Source: AJdET5cqjuz4yK7cYUR+j7nxDp98SiJKS2dq1OQUrR7cwr6S+jqQWu8hWACUA+so3KXCHURPrSI5 X-Received: by 2002:a63:fd53:: with SMTP id m19mr2606990pgj.340.1541453619596; Mon, 05 Nov 2018 13:33:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541453619; cv=none; d=google.com; s=arc-20160816; b=F1Ike1m3PzrxD75KROprrsyLAvZYJMok5H3DBJLkptZr/DwulaaPP/MirpZ7UKChCH L9LDM690Cmqu72NgMWLv5JjYcwzpytzjBxLhwc3m120R5BUZQfs9NYdNJeTCGEvbaqvY V38e4Hi+LID59JX3GJMLVs8xa0jwH8yxCw0XrSBHRnv09NADBKa38xK2I9jQzgwXzQVl wamQv0tmjub5hSh34Llst3Gb0MGAz276YRVVAChM/MN94PFh3efoJvsQUavrR7aVAgM6 f3TjPXYCw5iMNhI0p3dIZIxeSrQdmCucciEh/zkm9EYtldx6rC2bQytcEZEG+YcGuoQ9 DUew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=es6sn83DsjZ2o3p3EMzKWdnO4TfOxjtYsgKkLaMwZW4=; b=TNCu0Jqp7frICRXObgiSMVfKNWuRTACxpaXj08Ksh5RfXugV6VkxSohLfvVzXI61zL tXG1Zu3Ecy0N05MVhPGQNvjjkNaczfBryv3t12iAXZF7URCEvEvIhLFBRwqbKqEG1hjJ tWmxHO+IzPVAqEHuzGzRL2ZE04yujDLtRF/NAPmka/FZh2wDQ6qh56jB2Rvod0LSduDU iiDi1sX0XsPgv6sKZej67U47v79Gmt7Hdws2kAyDZq5tGhnsg+1g6cQmNW1p9iXOh9GY qJUW0bkTDZqQNuKMMhjevMgbO0TztsP3Cqq1ZFmagpK2uohDQMK9enuY7ndcN1LzjYHI +LJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QnGHu7jU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r63-v6si40847409plb.341.2018.11.05.13.33.24; Mon, 05 Nov 2018 13:33:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QnGHu7jU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388063AbeKFGxO (ORCPT + 99 others); Tue, 6 Nov 2018 01:53:14 -0500 Received: from mail-it1-f194.google.com ([209.85.166.194]:35534 "EHLO mail-it1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387441AbeKFGxN (ORCPT ); Tue, 6 Nov 2018 01:53:13 -0500 Received: by mail-it1-f194.google.com with SMTP id v11so8712030itj.0; Mon, 05 Nov 2018 13:31:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=es6sn83DsjZ2o3p3EMzKWdnO4TfOxjtYsgKkLaMwZW4=; b=QnGHu7jUyjhC82gNuz543MWkEKM0wLVVwXU6fqI27xDdVEc37Hfc/P6yLcoRNeFDZ8 nnLuBi4BKEQF2fh3vBTMAUW5emapk8sNbbe20eJJ4kt8dXBX89gXdH6G0CwKolP48s50 x8QOW3h9MfqCGx6mHXktB8jPqRXGxhWjiY7uLjnOXCiGTpWbgHX9xVYeo5Q9wgB2wyNG haaE/HcEBnJTvyjC3H3xLzfQBZ65NMYyYvkqrJH7HhQDWzM4Vx78cJ9I9l5z3MmKkvWy 4wZRyVQWtM/5hfscVM6dhuL0JEi/GNtRMt+S6jxmu06bqJdZ9TCbMRe774Pie/a4zizH blwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=es6sn83DsjZ2o3p3EMzKWdnO4TfOxjtYsgKkLaMwZW4=; b=DQrwv5O0vtu/RxQhjEmDObgfgyZSskE/9+qtYpAhqistDbfe4jI/nuuagMTyXL+1D9 VuikqYe0/S2vbNqsRxXV6gggo99AH2TgCi7pTRIKgKELZNAoFIYTNVN2CgoHaYQRI/b0 w3sN4s0nbKfYND8Vq2hCMi3bm1N4jm4zZVD61JmgNXb49j294tHTJ12Ey9iITMQdxvCJ iTibUjohTJ4+CEkQQmlATBRfM8WKqwU4hQMqi/dmQBM9OHXxRNmAfpExXladSqF3wHew KT4SM3OCQK9X7jyAsQHlbrmfXkt5qnGHORkejdwCkxycVQby84wlQ9nq/nhx+K70jtSV 59og== X-Gm-Message-State: AGRZ1gKP7/wnuUg3rlzc2vmETKPU0iIKdnITqtTfPYkCRfToWufcPGde zn0n/u1/XGt+zaE2UOwuLYOg1HxIr5Cdn1YDX9gh5bJo X-Received: by 2002:a02:4f9b:: with SMTP id r27-v6mr21812509jad.97.1541453492655; Mon, 05 Nov 2018 13:31:32 -0800 (PST) MIME-Version: 1.0 References: <1541079817-3431-1-git-send-email-firoz.khan@linaro.org> In-Reply-To: <1541079817-3431-1-git-send-email-firoz.khan@linaro.org> From: Matt Turner Date: Mon, 5 Nov 2018 13:31:20 -0800 Message-ID: Subject: Re: [PATCH v2 0/5] alpha: system call table generation support To: firoz.khan@linaro.org Cc: linux-alpha , Richard Henderson , Ivan Kokshaysky , Thomas Gleixner , Greg KH , Philippe Ombredanne , Kate Stewart , y2038@lists.linaro.org, LKML , linux-arch@vger.kernel.org, Arnd Bergmann , deepa.kernel@gmail.com, marcin.juszkiewicz@linaro.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 1, 2018 at 6:44 AM Firoz Khan wrote: > > The purpose of this patch series is, we can easily > add/modify/delete system call table support by cha- > nging 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 resp- > ective 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 correspond- > ing entry point. Add a new system call in this arch- > itecture will be possible by adding new entry in the > syscall.tbl file. Sounds like a worthy goal. I tried applying the patches and it seems they haven't been rebased since v4.18. My rebases are in https://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha.git/log/?h=for-linus They seem to work for me, FWIW. Is your plan to have the patches go through the separate architecture trees, or go in together? I think I'd at least prefer for another architecture to take the plunge before alpha.