From: Andreas Schwab <schwab@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: Siddhesh Poyarekar <siddhesh@redhat.com>,
libc-ports@sourceware.org, libc-alpha@sourceware.org
Subject: Re: PI mutex support for pthread_cond_* now in nptl
Date: Tue, 19 Feb 2013 17:01:00 -0000 [thread overview]
Message-ID: <mvmk3q4xmp2.fsf@hawking.suse.de> (raw)
In-Reply-To: <5123AB55.2070100__45742.2411222526$1361292204$gmane$org@twiddle.net> (Richard Henderson's message of "Tue, 19 Feb 2013 08:41:57 -0800")
Richard Henderson <rth@twiddle.net> writes:
> Any chance we can move these macros into a generic linux header?
What would that do to architectures that don't implement PI futexes?
Andreas.
--
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:[~2013-02-19 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 10:56 Siddhesh Poyarekar
2013-02-18 23:50 ` Joseph S. Myers
2013-02-19 0:50 ` Joseph S. Myers
2013-02-19 16:42 ` Richard Henderson
2013-02-19 16:49 ` Siddhesh Poyarekar
2013-02-19 17:18 ` Joseph S. Myers
2013-02-19 17:21 ` Siddhesh Poyarekar
2013-02-19 20:06 ` Torvald Riegel
2013-02-20 18:13 ` Steven Munroe
2013-02-20 20:25 ` Torvald Riegel
2013-02-20 22:04 ` Roland McGrath
2013-02-20 22:41 ` Steven Munroe
2013-02-21 4:32 ` Siddhesh Poyarekar
[not found] ` <1361304381.581.80.camel__6928.53579898856$1361304432$gmane$org@triegel.csb>
2013-02-22 4:11 ` Andi Kleen
[not found] ` <5123AB55.2070100__45742.2411222526$1361292204$gmane$org@twiddle.net>
2013-02-19 17:01 ` Andreas Schwab [this message]
2013-02-19 17:18 ` Siddhesh Poyarekar
2013-02-19 17:39 ` Andreas Schwab
2013-02-19 17:52 ` Siddhesh Poyarekar
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=mvmk3q4xmp2.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=rth@twiddle.net \
--cc=siddhesh@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).