From: Ingo Molnar <mingo@elte.hu>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: Daniel Walker <dwalker@mvista.com>,
tglx@linutronix.de, khilman@mvista.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] futex null pointer timeout
Date: Thu, 18 Jan 2007 14:07:25 +0100 [thread overview]
Message-ID: <20070118130725.GA14782@elte.hu> (raw)
In-Reply-To: <45AF6790.8010000@bull.net>
* Pierre Peiffer <pierre.peiffer@bull.net> wrote:
> Ingo Molnar a écrit :
> >* Daniel Walker <dwalker@mvista.com> wrote:
> >
> [...]
> >>The patch reworks do_futex, and futex_wait* so a NULL pointer in the
> >>timeout position is infinite, and anything else is evaluated as a real
> >>timeout.
> >
> >thanks, applied.
> >
>
> On top of this patch, you will need the following patch: futex_lock_pi
> is also involved.
thanks, applied. (FYI, your mailer added an extra space to every context
line in the patch and thus corrupted it, i fixed it up by hand.)
Ingo
prev parent reply other threads:[~2007-01-18 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 0:25 [PATCH] futex null pointer timeout Daniel Walker
2007-01-18 6:51 ` Thomas Gleixner
2007-01-18 7:38 ` Ingo Molnar
2007-01-18 12:26 ` Pierre Peiffer
2007-01-18 12:44 ` Daniel Walker
2007-01-18 13:07 ` Ingo Molnar [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=20070118130725.GA14782@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.peiffer@bull.net \
--cc=tglx@linutronix.de \
/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