Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1193203 > unrolled thread

Re: Next round: revised futex(2) man page for review

Started by"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
First post2015-07-27 16:50 +0200
Last post2015-07-27 16:50 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Next round: revised futex(2) man page for review "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> - 2015-07-27 16:50 +0200

#1193203 — Re: Next round: revised futex(2) man page for review

From"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Date2015-07-27 16:50 +0200
SubjectRe: Next round: revised futex(2) man page for review
Message-ID<pQRT4-4QW-9@gated-at.bofh.it>
On 07/27/2015 04:17 PM, Heinrich Schuchardt wrote:
> instruction. A thread maybe unable
> 
> to << missing word
> 
> acquire a lock because it is
> already acquired by another thread. It then may pass the lock's
> flag as futex word and the value representing the acquired state
> as the expected value to a futex() wait operation.

Thanks, Heinrich. Fixed.

Cheers,

Michael




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web