From: Joseph Myers <joseph@codesourcery.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>,
Firoz Khan <firoz.khan@linaro.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 0/6] mips: system call table generation support
Date: Thu, 6 Dec 2018 16:19:19 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1812061618110.12167@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.21.1812061209220.7193@eddie.linux-mips.org>
On Thu, 6 Dec 2018, Maciej W. Rozycki wrote:
> I believe this file is used by the glibc build process to retrieve
> syscall numbers for glibc's own use as well for <sys/syscall.h>. Has the
> change been verified not to break this process?
>
> Cc-ing <libc-alpha@sourceware.org> for information and possible further
> input.
I'm not sure what "this file" is. The glibc build uses the installed
<asm/unistd.h> (the results of #including it, not any other kind of
processing the file).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-12-06 16:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 8:43 [PATCH v3 0/6] mips: system call table generation support Firoz Khan
2018-11-29 8:43 ` [PATCH v3 1/6] mips: add __NR_syscalls along with __NR_Linux_syscalls Firoz Khan
2018-11-29 14:10 ` Arnd Bergmann
2018-11-30 4:45 ` Firoz Khan
2018-11-29 8:43 ` [PATCH v3 2/6] mips: remove unused macros Firoz Khan
2018-11-29 8:43 ` [PATCH v3 3/6] mips: add +1 to __NR_syscalls in uapi header Firoz Khan
2018-11-29 8:43 ` [PATCH v3 4/6] mips: remove syscall table entries Firoz Khan
2018-11-29 8:43 ` [PATCH v3 5/6] mips: add system call table generation support Firoz Khan
2018-11-29 14:15 ` Arnd Bergmann
2018-11-30 5:05 ` Firoz Khan
2018-11-29 8:43 ` [PATCH v3 6/6] mips: generate uapi header and system call table files Firoz Khan
2018-11-29 14:22 ` Arnd Bergmann
2018-11-30 5:13 ` Firoz Khan
2018-12-04 4:03 ` [PATCH v3 0/6] mips: system call table generation support Firoz Khan
2018-12-05 6:34 ` Paul Burton
2018-12-05 7:12 ` Firoz Khan
2018-12-06 12:15 ` Maciej W. Rozycki
2018-12-06 16:19 ` Joseph Myers [this message]
2018-12-06 17:02 ` Maciej W. Rozycki
2018-12-06 17:20 ` Joseph Myers
2018-12-06 17:43 ` Maciej W. Rozycki
2018-12-06 18:10 ` Florian Weimer
2018-12-07 14:33 ` Maciej W. Rozycki
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=alpine.DEB.2.21.1812061618110.12167@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhogan@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=paul.burton@mips.com \
--cc=pombredanne@nexb.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/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).