From: Dave McCracken <dmccr@us.ibm.com>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Separate CLONE_PARENT and CLONE_THREAD behavior
Date: Thu, 25 Oct 2001 08:24:12 -0500 [thread overview]
Message-ID: <3140000.1004016252@baldur> (raw)
In-Reply-To: <20011025021021.A2928@werewolf.able.es>
In-Reply-To: <117830000.1003951015@baldur> <20011025021021.A2928@werewolf.able.es>
--On Thursday, October 25, 2001 02:10:21 +0200 "J . A . Magallon"
<jamagallon@able.es> wrote:
> Will this break current pthreads in glibc 2.2.4 ???
No, the pthread library that comes with glibc doesn't use CLONE_THREAD.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
prev parent reply other threads:[~2001-10-25 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 19:16 [PATCH] Separate CLONE_PARENT and CLONE_THREAD behavior Dave McCracken
2001-10-25 0:10 ` J . A . Magallon
2001-10-25 13:24 ` Dave McCracken [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=3140000.1004016252@baldur \
--to=dmccr@us.ibm.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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