[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1344264832.27828.65.camel@twins>
Date: Mon, 06 Aug 2012 16:53:52 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Richard Weinberger <richard@....at>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
dvhart@...ux.intel.com, paul.gortmaker@...driver.com, jkosina@...e.cz,
rob@...dley.net, Randy Dunlap <rdunlap@...otime.net>, "Eric W. Biederman"
<ebiederm@...ssion.com>, David Howells <dhowells@...hat.com>, "Serge E.
Hallyn" <serge.hallyn@...onical.com>, kernel-hardening@...ts.openwall.com,
spender@...ecurity.net, keescook@...omium.org, tglx@...utronix.de, Cyrill
Gorcunov <gorcunov@...nvz.org>, xemul@...allels.com,
stable@...r.kernel.org, #@...gramming.kicks-ass.net,
3.4.x@...gramming.kicks-ass.net
Subject: Re: [PATCH] Revert "futex: Mark get_robust_list as deprecated"
On Fri, 2012-08-03 at 15:29 +0200, Richard Weinberger wrote:
> get_robust_list has at least two valid use cases.
> 1. checkpoint/restore in userspace
> 2. post mortem analysis
Shouldn't this then also be added as a comment somewhere near the
implementation to avoid a repeat of this deprecate / undeprecate cycle?
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
