From: Alistair Francis <alistair23@gmail.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] linux: Fix syscall list generation instructions
Date: Thu, 9 Jul 2020 06:42:27 -0700 [thread overview]
Message-ID: <CAKmqyKOHRupdy8-MNKv__gN4UMkY+0Fxr6V-+8ywTSgEYwvLOQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2007090520150.24175@redsun52.ssa.fujisawa.hgst.com>
On Wed, Jul 8, 2020 at 9:40 PM Maciej W. Rozycki via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Make the instructions for syscall list generation match Makefile and
> refer to `update-syscall-lists'; there has been no `update-arch-syscall'
> target. Also use single quotes around the command to stick to the ASCII
> character set.
>
> Fixes 4cf0d223052d ("Linux: Add tables with system call numbers").
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
> ---
> As a fix to a Makefile comment only I trust it is fine to apply even in
> the freeze period. OK to push then?
>
> Maciej
> ---
> sysdeps/unix/sysv/linux/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> glibc-update-syscall-lists.diff
> Index: glibc/sysdeps/unix/sysv/linux/Makefile
> ===================================================================
> --- glibc.orig/sysdeps/unix/sysv/linux/Makefile
> +++ glibc/sysdeps/unix/sysv/linux/Makefile
> @@ -26,7 +26,7 @@ ifndef subdir
> # architecture-specific system call names.
> #
> # To bootstrap a new architecture, create an empty file in the right
> -# place and run ?make update-arch-syscall? from the top-level of a
> +# place and run `make update-syscall-lists' from the top-level of a
> # configured, but not-yet-built glibc tree.
> #
> # --lock points to a file not replaced during the update operation, so
next prev parent reply other threads:[~2020-07-09 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 4:40 Maciej W. Rozycki
2020-07-09 13:42 ` Alistair Francis [this message]
2020-07-09 15:08 ` Carlos O'Donell
2020-07-09 16:47 ` 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=CAKmqyKOHRupdy8-MNKv__gN4UMkY+0Fxr6V-+8ywTSgEYwvLOQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@wdc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).