Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263202AbTEOAdp (ORCPT ); Wed, 14 May 2003 20:33:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263246AbTEOAdp (ORCPT ); Wed, 14 May 2003 20:33:45 -0400 Received: from pao-ex01.pao.digeo.com ([12.47.58.20]:40380 "EHLO pao-ex01.pao.digeo.com") by vger.kernel.org with ESMTP id S263202AbTEOAdo (ORCPT ); Wed, 14 May 2003 20:33:44 -0400 Date: Wed, 14 May 2003 17:41:58 -0700 From: Andrew Morton To: "Perez-Gonzalez, Inaky" Cc: ch@murgatroid.com, hch@infradead.org, linux-kernel@vger.kernel.org, torvalds@transmeta.com Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional Message-Id: <20030514174158.47c2a3b5.akpm@digeo.com> In-Reply-To: References: X-Mailer: Sylpheed version 0.8.9 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 May 2003 00:46:29.0000 (UTC) FILETIME=[6BE56080:01C31A7B] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 577 Lines: 13 "Perez-Gonzalez, Inaky" wrote: > > How does this affect mm_release() in fork.c? there is a call to sys_futex(); > if you make it conditional, will it break anything in there? Via linker magic, mm_release() will simply call sys_ni_syscall() instead. (I ran a futex-free ppc64 kernel. It worked.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/