From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clone.2: fix a bug of CLONE_PARENT_SETTID
Date: Thu, 05 Feb 2015 13:48:48 +0100 [thread overview]
Message-ID: <54D366B0.7040007@gmail.com> (raw)
In-Reply-To: <1383903679-11598-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 11/08/2013 10:41 AM, Peng Haitao wrote:
> CLONE_PARENT_SETTID only stores child thread ID in parent memory.
Applied. Thanks, Haitao.
Cheers,
Michael
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man2/clone.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/clone.2 b/man2/clone.2
> index 4815fb1..6325397 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -532,7 +532,7 @@ calling process itself, will be signaled.
> .BR CLONE_PARENT_SETTID " (since Linux 2.5.49)"
> Store child thread ID at location
> .I ptid
> -in parent and child memory.
> +in parent memory.
> (In Linux 2.5.32-2.5.48 there was a flag
> .B CLONE_SETTID
> that did this.)
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-02-05 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 9:41 [PATCH] clone.2: fix a bug of CLONE_PARENT_SETTID Peng Haitao
[not found] ` <1383903679-11598-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-02-05 12:48 ` Michael Kerrisk (man-pages) [this message]
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=54D366B0.7040007@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.