public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] trivial doc fix: remove weird phrase "syscall takes zero to five arguments"
Date: Wed, 14 Feb 2024 16:59:44 +0000 (GMT)	[thread overview]
Message-ID: <20240214165944.28AD5385E448@sourceware.org> (raw)

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

commit dbae3a3940940977b8b8190a145a444732846219
Author: Askar Safin <safinaskar@zohomail.com>
Date:   Mon Feb 12 19:48:55 2024 +0300

    trivial doc fix: remove weird phrase "syscall takes zero to five arguments"
    
    "number of arguments, from zero to five" is wrong, because on Linux maximal number
    of arguments is 6, not 5. Also, maximal number of arguments is kernel-dependent,
    so let's not include it here at all.
    
    Moreover, "Each kind of system call has a definite number of arguments" is questionable.
    Think about SYS_open on Linux, which takes 2 or 3 arguments. Or SYS_clone on Linux x86_64, which
    takes 2 to 5 arguments. So I propose to fully remove this sentence.
    
    Signed-off-by: Askar Safin <safinaskar@zohomail.com>
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

Diff:
---
 manual/startup.texi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/manual/startup.texi b/manual/startup.texi
index 9bf24123f5..96a7a472bb 100644
--- a/manual/startup.texi
+++ b/manual/startup.texi
@@ -727,8 +727,7 @@ identified by a number.  Macros for all the possible system call numbers
 are defined in @file{sys/syscall.h}
 
 The remaining arguments are the arguments for the system call, in
-order, and their meanings depend on the kind of system call.  Each kind
-of system call has a definite number of arguments, from zero to five.
+order, and their meanings depend on the kind of system call.
 If you code more arguments than the system call takes, the extra ones to
 the right are ignored.

                 reply	other threads:[~2024-02-14 16:59 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=20240214165944.28AD5385E448@sourceware.org \
    --to=azanella@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).