public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "allan at archlinux dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/12403] futex issues with --enable-kernel=2.6.22 to 2.6.28
Date: Mon, 24 Jan 2011 23:00:00 -0000 [thread overview]
Message-ID: <bug-12403-131-TOe1uEikFk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12403-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12403
Allan McRae <allan at archlinux dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |
--- Comment #6 from Allan McRae <allan at archlinux dot org> 2011-01-24 05:17:46 UTC ---
Thanks. I can confirm that patch fixes the issues I was observing.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-24 5:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 9:39 [Bug nptl/12403] New: " allan at archlinux dot org
2011-01-16 9:53 ` [Bug nptl/12403] " allan at archlinux dot org
2011-01-16 22:50 ` drepper.fsp at gmail dot com
2011-01-17 22:55 ` allan at archlinux dot org
2011-01-23 22:38 ` bz-glibc at kdzbn dot homelinux.net
2011-01-24 5:17 ` bz-glibc at kdzbn dot homelinux.net
2011-01-24 23:00 ` allan at archlinux dot org [this message]
2011-02-14 4:52 ` vapier at gentoo dot org
2011-07-25 9:44 ` j at bitron dot ch
2011-08-18 6:52 ` schwab@linux-m68k.org
2011-09-09 3:56 ` drepper.fsp at gmail dot com
2012-01-09 19:39 ` vapier at gentoo dot org
2012-01-10 7:12 ` bz-glibc at kdzbn dot homelinux.net
2012-01-10 21:04 ` vapier at gentoo dot org
2014-02-16 17:45 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-27 12:25 ` fweimer at redhat dot com
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-12403-131-TOe1uEikFk@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.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).