From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v3 01/29] asm-generic: add generic futex for !CONFIG_SMP Date: Tue, 23 Sep 2014 12:40:54 +0200 Message-ID: <13000968.l0laEvMsix@wuerfel> References: <1410168160-3624-1-git-send-email-lftan@altera.com> <1410168160-3624-2-git-send-email-lftan@altera.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: "LF.Tan" Cc: Linux-Arch , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , Ley Foon Tan , Chung-Lin Tang List-Id: linux-arch.vger.kernel.org On Tuesday 23 September 2014 18:20:08 LF.Tan wrote: > Hi Arnd > > Are you okay with this generic futex in asm-generic? > Yes, this looks good. Remind me again who need this, would it make sense to merge this through an architecture-specific tree for whichever architecture can benefit from it? Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.126.131]:50042 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754580AbaIWKk6 (ORCPT ); Tue, 23 Sep 2014 06:40:58 -0400 From: Arnd Bergmann Subject: Re: [PATCH v3 01/29] asm-generic: add generic futex for !CONFIG_SMP Date: Tue, 23 Sep 2014 12:40:54 +0200 Message-ID: <13000968.l0laEvMsix@wuerfel> In-Reply-To: References: <1410168160-3624-1-git-send-email-lftan@altera.com> <1410168160-3624-2-git-send-email-lftan@altera.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-arch-owner@vger.kernel.org List-ID: To: "LF.Tan" Cc: Linux-Arch , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , Ley Foon Tan , Chung-Lin Tang Message-ID: <20140923104054.khh6bq7USlt6hS8RXWTsYJmlKDCTy64iwqoP_u588vw@z> On Tuesday 23 September 2014 18:20:08 LF.Tan wrote: > Hi Arnd > > Are you okay with this generic futex in asm-generic? > Yes, this looks good. Remind me again who need this, would it make sense to merge this through an architecture-specific tree for whichever architecture can benefit from it? Arnd