From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Maciej W. Rozycki" Subject: Re: [PATCH v3 0/6] mips: system call table generation support Date: Thu, 6 Dec 2018 17:02:28 +0000 (GMT) Message-ID: References: <1543481016-18500-1-git-send-email-firoz.khan@linaro.org> <20181205063436.kzxgnvgexcgq572k@pburton-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23990824AbeLFRC2KGuYc (ORCPT + 1 other); Thu, 6 Dec 2018 18:02:28 +0100 In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Joseph Myers Cc: Paul Burton , Firoz Khan , "open list:RALINK MIPS ARCHITECTURE" , Ralf Baechle , James Hogan , Greg Kroah-Hartman , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , y2038 Mailman List , Arnd Bergmann , Linux Kernel Mailing List , Linux-Arch , Deepa Dinamani , Marcin Juszkiewicz , libc-alpha@sourceware.org List-Id: linux-arch.vger.kernel.org On Thu, 6 Dec 2018, Joseph Myers wrote: > > I believe this file is used by the glibc build process to retrieve > > syscall numbers for glibc's own use as well for . Has the > > change been verified not to break this process? > > > > Cc-ing for information and possible further > > input. > > I'm not sure what "this file" is. The glibc build uses the installed > (the results of #including it, not any other kind of > processing the file). So how are `SYS_' macros generated that land in ? Maciej From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eddie.linux-mips.org ([148.251.95.138]:39946 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725889AbeLFREJ (ORCPT ); Thu, 6 Dec 2018 12:04:09 -0500 Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S23990824AbeLFRC2KGuYc (ORCPT + 1 other); Thu, 6 Dec 2018 18:02:28 +0100 Date: Thu, 6 Dec 2018 17:02:28 +0000 (GMT) From: "Maciej W. Rozycki" Subject: Re: [PATCH v3 0/6] mips: system call table generation support In-Reply-To: Message-ID: References: <1543481016-18500-1-git-send-email-firoz.khan@linaro.org> <20181205063436.kzxgnvgexcgq572k@pburton-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-arch-owner@vger.kernel.org List-ID: To: Joseph Myers Cc: Paul Burton , Firoz Khan , "open list:RALINK MIPS ARCHITECTURE" , Ralf Baechle , James Hogan , Greg Kroah-Hartman , Philippe Ombredanne , Thomas Gleixner , Kate Stewart , y2038 Mailman List , Arnd Bergmann , Linux Kernel Mailing List , Linux-Arch , Deepa Dinamani , Marcin Juszkiewicz , libc-alpha@sourceware.org Message-ID: <20181206170228.DjB_FUcurHu8YJ0BPhAFfyQdl5uN_U4NWNI4lA1oh8w@z> On Thu, 6 Dec 2018, Joseph Myers wrote: > > I believe this file is used by the glibc build process to retrieve > > syscall numbers for glibc's own use as well for . Has the > > change been verified not to break this process? > > > > Cc-ing for information and possible further > > input. > > I'm not sure what "this file" is. The glibc build uses the installed > (the results of #including it, not any other kind of > processing the file). So how are `SYS_' macros generated that land in ? Maciej