public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davem at davemloft dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/16882] Incorrect implementation of pthread_spin_lock for sparc, no ldstub after spinning Date: Wed, 04 Jun 2014 01:22:00 -0000 [thread overview] Message-ID: <bug-16882-131-lXeFsZn8V8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16882-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16882 David S. Miller <davem at davemloft dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #12 from David S. Miller <davem at davemloft dot net> --- Fixed in mainline and all relevant branches. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-04 1:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-29 18:39 [Bug nptl/16882] New: " a5b at mail dot ru 2014-05-23 4:33 ` [Bug nptl/16882] " culu.gyx at gmail dot com 2014-05-23 4:33 ` culu.gyx at gmail dot com 2014-05-23 4:36 ` culu.gyx at gmail dot com 2014-05-23 14:26 ` culu.gyx at gmail dot com 2014-05-23 14:34 ` Ondřej Bílka 2014-05-23 14:35 ` neleai at seznam dot cz 2014-05-23 15:09 ` culu.gyx at gmail dot com 2014-05-25 2:12 ` culu.gyx at gmail dot com 2014-05-30 4:38 ` davem at davemloft dot net 2014-06-03 23:11 ` cvs-commit at gcc dot gnu.org 2014-06-03 23:42 ` cvs-commit at gcc dot gnu.org 2014-06-04 0:19 ` cvs-commit at gcc dot gnu.org 2014-06-04 0:58 ` cvs-commit at gcc dot gnu.org 2014-06-04 1:19 ` cvs-commit at gcc dot gnu.org 2014-06-04 1:22 ` davem at davemloft dot net [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=bug-16882-131-lXeFsZn8V8@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).