From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v9 2/6] mips: Add the clone3 wrapper
Date: Mon, 04 Sep 2023 14:04:44 +0200 [thread overview]
Message-ID: <87zg22xhyb.fsf@oldenburg3.str.redhat.com> (raw)
In-Reply-To: <20230824164219.391263-3-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Thu, 24 Aug 2023 13:42:15 -0300")
* Adhemerval Zanella:
> It follows the internal signature:
>
> extern int clone3 (struct clone_args *__cl_args, size_t __size,
> int (*__func) (void *__arg), void *__arg);
>
> Checked on mips64el-linux-gnueabihf, mips64el-n32-linux-gnu, and
> mipsel-linux-gnu.
It should be okay, but I'm not familiar with MIPS, so I can't review
this for real. I suppose you could push this without review.
Thanks,
Florian
next prev parent reply other threads:[~2023-09-04 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 16:42 [PATCH v9 0/6] Add pidfd and cgroupv2 support for process creation Adhemerval Zanella
2023-08-24 16:42 ` [PATCH v9 1/6] arm: Add the clone3 wrapper Adhemerval Zanella
2023-09-04 12:04 ` Florian Weimer
2023-09-05 13:14 ` Adhemerval Zanella Netto
2023-08-24 16:42 ` [PATCH v9 2/6] mips: " Adhemerval Zanella
2023-09-04 12:04 ` Florian Weimer [this message]
2023-09-05 13:15 ` Adhemerval Zanella Netto
2023-08-24 16:42 ` [PATCH v9 3/6] linux: Define __ASSUME_CLONE3 to 0 for alpha, ia64, nios2, sh, and sparc Adhemerval Zanella
2023-08-24 16:42 ` [PATCH v9 4/6] linux: Add posix_spawnattr_{get,set}cgroup_np (BZ 26731) Adhemerval Zanella
2023-08-24 16:42 ` [PATCH v9 5/6] posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349) Adhemerval Zanella
2023-09-04 12:53 ` Florian Weimer
2023-08-24 16:42 ` [PATCH v9 6/6] linux: Add pidfd_getpid Adhemerval Zanella
2023-08-28 12:42 ` [PATCH v9 0/6] Add pidfd and cgroupv2 support for process creation Luca Boccassi
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=87zg22xhyb.fsf@oldenburg3.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--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).