public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/release/2.34/master] Update syscall-names.list for Linux 5.18
Date: Thu, 21 Jul 2022 15:27:17 +0000 (GMT)	[thread overview]
Message-ID: <20220721152717.11A4E3858280@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b991af50632a2da262b00b2375d9120f23b25525

commit b991af50632a2da262b00b2375d9120f23b25525
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed May 25 14:37:28 2022 +0000

    Update syscall-names.list for Linux 5.18
    
    Linux 5.18 has no new syscalls.  Update the version number in
    syscall-names.list to reflect that it is still current for 5.18.
    
    Tested with build-many-glibcs.py.
    
    (cherry picked from commit 3d9926663cba19f40d26d8a8ab3b2a7cc09ffb13)

Diff:
---
 sysdeps/unix/sysv/linux/syscall-names.list | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/syscall-names.list b/sysdeps/unix/sysv/linux/syscall-names.list
index e2743c6495..95370e2ec5 100644
--- a/sysdeps/unix/sysv/linux/syscall-names.list
+++ b/sysdeps/unix/sysv/linux/syscall-names.list
@@ -21,8 +21,8 @@
 # This file can list all potential system calls.  The names are only
 # used if the installed kernel headers also provide them.
 
-# The list of system calls is current as of Linux 5.17.
-kernel 5.17
+# The list of system calls is current as of Linux 5.18.
+kernel 5.18
 
 FAST_atomic_update
 FAST_cmpxchg


                 reply	other threads:[~2022-07-21 15:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220721152717.11A4E3858280@sourceware.org \
    --to=fw@sourceware.org \
    --cc=glibc-cvs@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).