public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: alx@kernel.org, libc-alpha@sourceware.org
Subject: Re: [patch v3] manual: add syscall list
Date: Wed, 22 May 2024 15:40:27 -0400	[thread overview]
Message-ID: <xn34q98wk4.fsf@greed.delorie.com> (raw)
In-Reply-To: <e718cc34-1109-4e34-a36b-8eb37e0f719f@redhat.com> (carlos@redhat.com)

"Carlos O'Donell" <carlos@redhat.com> writes:
>> +# Generate a list of wrapped syscalls
>
> s/wrapped syscalls/syscall wrappers (non-cancellable)... /g

Fixed.

> s/Cancelled/... and cancellable syscall wrappers/g

Fixed.

>> +$(objpfx)syscalls.texi: $(objpfx)stamp-syscalls ;
>> +$(objpfx)stamp-syscalls: $(common-objpfx)config.make
>> +	cat `find ../sysdeps -name syscalls.list -print` \
>
> OK. This scans *all targets* and generates *all syscalls* regardless of if the
> configuration is used or unused. This makes the list architecture agnostic. We
> will need to say something about that later.
>
>> +documentation is considered authoritative.
>
> This needs extra information to say that this list covers all targets provided by glibc.

I changed the prelude to each list to be such:

  Here is the list of all potential non-cancellable system calls, across
  all configurations of @theglibc():

  Here's the corresponding list of cancellable system calls:

I think that covers both these requests.

> When posting v4 may you please post a PDF of the final results from `make pdf?`

I'll attach it in a separate email in case the mail filters are having a
bad day ;-)


  reply	other threads:[~2024-05-22 19:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 20:52 manual: add syscall list appendix DJ Delorie
2024-05-16  5:02 ` Florian Weimer
2024-05-16 11:44   ` Carlos O'Donell
2024-05-16 12:06     ` Florian Weimer
2024-05-16 13:37     ` Alejandro Colomar
2024-05-16 14:52       ` Carlos O'Donell
2024-05-16 15:03         ` Alejandro Colomar
2024-05-16 17:57       ` DJ Delorie
2024-05-16 17:55     ` DJ Delorie
2024-05-16 21:08       ` Alejandro Colomar
2024-05-17 13:21       ` Carlos O'Donell
2024-05-17 15:31         ` DJ Delorie
2024-05-17 19:16           ` Carlos O'Donell
2024-05-20 21:43             ` [patch v2] manual: add syscall list DJ Delorie
2024-05-20 22:10               ` Alejandro Colomar
2024-05-21  1:12                 ` DJ Delorie
2024-05-21 10:22                   ` Alejandro Colomar
2024-05-21 17:16                     ` DJ Delorie
2024-05-21 20:04                 ` [patch v3] " DJ Delorie
2024-05-22 19:07                   ` Carlos O'Donell
2024-05-22 19:40                     ` DJ Delorie [this message]
2024-05-22 19:41                     ` [patch v4] " DJ Delorie
2024-05-22 19:42                       ` DJ Delorie
2024-05-22 20:54                       ` Florian Weimer
2024-05-22 21:00                         ` Florian Weimer
2024-05-22 21:26                         ` DJ Delorie
2024-05-23  7:31                           ` Florian Weimer
2024-05-23  8:49                             ` Andreas Schwab
2024-05-22 22:45                       ` DJ Delorie
2024-05-22 23:12                       ` Alejandro Colomar
2024-05-23 16:59                       ` Zack Weinberg
2024-05-23 19:38                         ` DJ Delorie
2024-05-23 19:41                           ` Zack Weinberg
2024-05-23 19:46                             ` DJ Delorie
2024-05-23 19:51                             ` Joseph Myers
2024-05-23 21:18                         ` Alejandro Colomar
2024-05-16 17:37   ` manual: add syscall list appendix DJ Delorie
2024-05-16 17:55     ` Joe Simmons-Talbott

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=xn34q98wk4.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.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).