From: Askar Safin <safinaskar@zohomail.com>
To: "Rich Felker" <dalias@libc.org>
Cc: "Florian Weimer" <fweimer@redhat.com>,
"libc-alpha" <libc-alpha@sourceware.org>,
"adhemerval.zanella" <adhemerval.zanella@linaro.org>,
"carlos" <carlos@redhat.com>
Subject: Re: [PATCH v2] Add public function syscall_no_errno
Date: Mon, 12 Feb 2024 20:16:56 +0400 [thread overview]
Message-ID: <18d9e1b74fd.108074ea744834.1983132793117906544@zohomail.com> (raw)
In-Reply-To: <20240212144439.GO22081@brightrain.aerifal.cx>
---- On Mon, 12 Feb 2024 18:44:31 +0400 Rich Felker wrote ---
> Yes, there are a very small number of such syscalls -- getuid and
> getgid are the only relevant ones AFAICT -- but the author of this
> proposal is missing the point
Okay, I declare defeat
--
Askar Safin
https://types.pl/@safinaskar
next prev parent reply other threads:[~2024-02-12 16:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 16:39 [PATCH, RFC] " Askar Safin
2024-02-01 17:53 ` Adhemerval Zanella Netto
2024-02-01 18:18 ` Rich Felker
2024-02-01 19:32 ` Askar Safin
2024-02-01 20:16 ` dalias
2024-02-01 20:57 ` Adhemerval Zanella Netto
2024-02-08 15:02 ` [PATCH v2] " Askar Safin
2024-02-08 17:48 ` Szabolcs Nagy
2024-02-12 14:24 ` Florian Weimer
2024-02-12 14:44 ` Rich Felker
2024-02-12 16:16 ` Askar Safin [this message]
2024-02-12 17:25 ` Zack Weinberg
2024-02-12 17:43 ` Andreas Schwab
2024-02-12 18:22 ` Zack Weinberg
2024-02-13 9:10 ` Andreas Schwab
2024-02-13 11:57 ` Adhemerval Zanella Netto
2024-02-12 17:55 ` Adhemerval Zanella Netto
2024-02-12 18:34 ` Askar Safin
2024-02-07 0:59 ` [PATCH, RFC] " Askar Safin
2024-02-07 20:59 ` dalias
2024-02-08 17:08 ` Askar Safin
2024-02-07 1:57 ` Mike Frysinger
2024-02-07 12:55 ` Askar Safin
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=18d9e1b74fd.108074ea744834.1983132793117906544@zohomail.com \
--to=safinaskar@zohomail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=fweimer@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).