From: Andrew Morton <akpm@osdl.org>
To: chaosite@gmail.com
Cc: daviado@gmail.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
drepper@gmail.com, robustmutexes@lists.osdl.org
Subject: Re: Robust futex patch for Linux 2.6.15
Date: Sat, 14 Jan 2006 12:25:21 -0800 [thread overview]
Message-ID: <20060114122521.39f86ed5.akpm@osdl.org> (raw)
In-Reply-To: <43C9233A.20504@gmail.com>
Matan Peled <chaosite@gmail.com> wrote:
>
> Andrew, I'm looking at this:
>
> http://source.mvista.com/~dsingleton/robust-futex-1
>
> And it doesn't seem to have a futex_deadlock function at all. In fact, its seems
> to have a rather lengthy description about robust futexes and why they're a Good
> Thing(TM).
>
> What are you looking at?
A file which now appears to have been deleted..
next prev parent reply other threads:[~2006-01-14 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b324b5ad0601131316m721f959eu37b741f9e5557a2e@mail.gmail.com>
2006-01-13 21:27 ` Robust futex patch for Linux 2.6.15 Andrew Morton
2006-01-13 22:20 ` Andi Kleen
2006-01-13 23:01 ` Andrew Morton
2006-01-14 16:13 ` Matan Peled
2006-01-14 20:25 ` Andrew Morton [this message]
2006-01-16 19:09 ` Re [robust-futex-2] : interdiff for memory leak fix david singleton
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=20060114122521.39f86ed5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=chaosite@gmail.com \
--cc=daviado@gmail.com \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robustmutexes@lists.osdl.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: 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 NNTP newsgroup(s).