[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.21.1812061209220.7193@eddie.linux-mips.org>
Date: Thu, 6 Dec 2018 12:15:41 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Paul Burton <paul.burton@...s.com>
cc: Firoz Khan <firoz.khan@...aro.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@...ux-mips.org>,
Ralf Baechle <ralf@...ux-mips.org>,
James Hogan <jhogan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>,
Kate Stewart <kstewart@...uxfoundation.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
Deepa Dinamani <deepa.kernel@...il.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>,
libc-alpha@...rceware.org
Subject: Re: [PATCH v3 0/6] mips: system call table generation support
On Wed, 5 Dec 2018, Paul Burton wrote:
> > Could you review this patch series. I would appreciate if you can
> > perform the boot test on the actual platform.
>
> This is looking pretty good to me, so I look forward to v4 with Arnd's
> comments addressed.
>
> I've verified that the sys call tables are identical for both
> 32r2el_defconfig & 64r6el_defconfig before & after this series, and that
> both still boot fine.
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@...rceware.org> for information and possible further
input.
Maciej
Powered by blists - more mailing lists