From: Andreas Schwab <schwab@suse.de>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: jakub@redhat.com, sebastien.dugue@bull.net, arjan@infradead.org,
mingo@redhat.com, linux-kernel@vger.kernel.org,
pierre.peiffer@bull.net, drepper@redhat.com
Subject: Re: NPTL mutex and the scheduling priority
Date: Thu, 07 Sep 2006 11:37:54 +0200 [thread overview]
Message-ID: <je7j0grp8t.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060907.183013.55145698.nemoto@toshiba-tops.co.jp> (Atsushi Nemoto's message of "Thu, 07 Sep 2006 18:30:13 +0900 (JST)")
Atsushi Nemoto <nemoto@toshiba-tops.co.jp> writes:
> And ENOTSUP is not enumerated in ERRORS section of pthread_mutex_init.
POSIX does not forbid additional error conditions, as long as the
described conditions are properly reported with the documented error
numbers.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-09-07 9:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 8:10 NPTL mutex and the scheduling priority Atsushi Nemoto
2006-06-12 12:23 ` Arjan van de Ven
2006-06-12 12:44 ` Jakub Jelinek
2006-06-12 15:24 ` Sébastien Dugué
2006-06-12 16:06 ` Atsushi Nemoto
2006-09-07 8:11 ` Atsushi Nemoto
2006-09-07 8:32 ` Jakub Jelinek
2006-09-07 9:30 ` Atsushi Nemoto
2006-09-07 9:37 ` Andreas Schwab [this message]
2006-09-07 9:42 ` Atsushi Nemoto
2006-06-13 8:39 ` Pierre Peiffer
2006-06-13 8:48 ` Jakub Jelinek
2006-06-13 12:04 ` Sébastien Dugué
2006-06-13 12:56 ` Jakub Jelinek
2006-06-14 13:19 ` Sébastien Dugué
2006-06-14 13:28 ` Jakub Jelinek
2006-06-14 13:38 ` Pierre Peiffer
2006-06-15 9:28 ` Pierre Peiffer
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=je7j0grp8t.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nemoto@toshiba-tops.co.jp \
--cc=pierre.peiffer@bull.net \
--cc=sebastien.dugue@bull.net \
/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