From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Update syscall lists for Linux 5.15
Date: Wed, 10 Nov 2021 10:06:01 +0100 [thread overview]
Message-ID: <87pmr8753a.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2111042038520.2137366@digraph.polyomino.org.uk> (Joseph Myers's message of "Thu, 4 Nov 2021 20:39:14 +0000")
* Joseph Myers:
> Linux 5.15 has one new syscall, process_mrelease (and also enables the
> clone3 syscall for RV32). It also has a macro __NR_SYSCALL_MASK for
> Arm, which is not a syscall but matches the pattern used for syscall
> macro names.
>
> Add __NR_SYSCALL_MASK to the names filtered out in the code dealing
> with syscall lists, update syscall-names.list for the new syscall and
> regenerate the arch-syscall.h headers with build-many-glibcs.py
> update-syscalls.
>
> Tested with build-many-glibcs.py.
Looks good to me.
Thanks,
Florian
prev parent reply other threads:[~2021-11-10 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 20:39 Joseph Myers
2021-11-08 15:03 ` Ping " Joseph Myers
2021-11-10 9:06 ` Florian Weimer [this message]
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=87pmr8753a.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).