From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Avoid cancellation point in pthread_mutex_lock etc. in linuxthreads
Date: Tue, 01 Apr 2003 20:46:00 -0000 [thread overview]
Message-ID: <3E89FA7B.6090506@redhat.com> (raw)
In-Reply-To: <20030401201745.GM16629@sunsite.ms.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jakub Jelinek wrote:
> It differs between arches.
It's not worth adding much cmoplexity. I think the original patch is fine.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+ifp72ijCOnn/RHQRAreBAJkBsME5UcHaG3YjFA41Vvi3t8PV5ACcDsp4
LcBHA+NKhtrhK2cjZPQ/vs4=
=iUfj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-04-01 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 15:19 Jakub Jelinek
2003-04-01 19:50 ` Roland McGrath
2003-04-01 20:17 ` Jakub Jelinek
2003-04-01 20:46 ` Ulrich Drepper [this message]
2003-04-02 0:11 ` Roland McGrath
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=3E89FA7B.6090506@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.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).