From: Rusty Russell <rusty@rustcorp.com.au>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Patch] Removal of FUTEX_FD
Date: Tue, 29 Jan 2008 13:55:37 +1100 [thread overview]
Message-ID: <200801291355.38121.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080125094046.GA4494@alice>
On Friday 25 January 2008 20:40:46 Eric Sesterhenn wrote:
> hi,
>
> since FUTEX_FD was scheduled for removal in June 2007 lets remove it.
> Google Code search found no users for it and NGPT was abandoned in 2003
> according to IBM. futex.h is left untouched to make sure the id does
> not get reassigned. Since queue_me() has no users left it is commented
> out to avoid a warning, i didnt remove it completely since it is part
> of the internal api (matching unqueue_me())
Thanks, I've queued this with a futher cleanup (rename __queue_me to queue_me,
add comments, and remove the old one entirely).
Thanks,
Rusty.
next prev parent reply other threads:[~2008-01-29 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 9:40 [Patch] Removal of FUTEX_FD Eric Sesterhenn
2008-01-29 2:55 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-05 7:59 [PATCH] " Rusty Russell
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=200801291355.38121.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snakebyte@gmx.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