From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Florian Weimer <fweimer@redhat.com>,
Luca Boccassi <luca.boccassi@gmail.com>,
Philip Withnall <bugzilla@tecnocode.co.uk>
Subject: Re: [PATCH v4 1/3] posix: Add pidfd_spawn and pidfd_spawnp (BZ# 30349)
Date: Mon, 22 May 2023 12:46:25 +0200 [thread overview]
Message-ID: <mvm1qj8hce6.fsf@suse.de> (raw)
In-Reply-To: <87zg5w4piy.fsf@oldenburg3.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 22 May 2023 12:41:09 +0200")
On Mai 22 2023, Florian Weimer via Libc-alpha wrote:
>> diff --git a/sysdeps/unix/sysv/linux/clone-pidfd-support.c b/sysdeps/unix/sysv/linux/clone-pidfd-support.c
>> new file mode 100644
>> index 0000000000..4bf2317c17
>> --- /dev/null
>> +++ b/sysdeps/unix/sysv/linux/clone-pidfd-support.c
>
>> + Also tThe waitid is a cancellation entrypoint, so issue the syscall
>> + directly. */
>
> Typo: “tThe”
It should be removed altogether, since waitid is a proper name.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-05-22 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 17:35 [PATCH v4 0/3] Add pidfd_spawn, pidfd_spawnp, pidfd_fork, and pidfd_getpid Adhemerval Zanella
2023-05-17 17:35 ` [PATCH v4 1/3] posix: Add pidfd_spawn and pidfd_spawnp (BZ# 30349) Adhemerval Zanella
2023-05-22 10:41 ` Florian Weimer
2023-05-22 10:46 ` Andreas Schwab [this message]
2023-05-22 14:18 ` Adhemerval Zanella Netto
2023-05-17 17:35 ` [PATCH v4 2/3] posix: Add pidfd_fork Adhemerval Zanella
2023-05-22 10:12 ` Florian Weimer
2023-05-22 12:44 ` Christian Brauner
2023-05-22 14:48 ` Adhemerval Zanella Netto
2023-05-17 17:35 ` [PATCH v4 3/3] linux: Add pidfd_getpid Adhemerval Zanella
2023-05-22 13:00 ` Florian Weimer
2023-05-22 17:13 ` Adhemerval Zanella Netto
2023-05-22 13:53 ` 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=mvm1qj8hce6.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=bugzilla@tecnocode.co.uk \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=luca.boccassi@gmail.com \
/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).