From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752054AbaIXLKJ (ORCPT ); Wed, 24 Sep 2014 07:10:09 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:53861 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750725AbaIXLKG (ORCPT ); Wed, 24 Sep 2014 07:10:06 -0400 From: Arnd Bergmann To: Ley Foon Tan Cc: Linux-Arch , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , Chung-Lin Tang , Thomas Gleixner Subject: Re: [PATCH v3 01/29] asm-generic: add generic futex for !CONFIG_SMP Date: Wed, 24 Sep 2014 13:10 +0200 Message-ID: <3608975.MxU44B73lk@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <1410168160-3624-1-git-send-email-lftan@altera.com> <12538756.JybTPMqFHj@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:6n30kICWNisCi0XOZnEcm9Y1dIDArudoOODbZtz7Lld uNroZfda40O9Qt9pD2Hf3G8cwKYC3MIR0YJP2Dbypo1DwC8v7T uJ3Q2xnL7IYGWa+liF5a6fc6DQ2q/9mc6C5T9wll9tu7XFB2+o dXwnU6iOr7616sY1Hjg1k5okUBoG1Ii/rLrJOuSrZli7vOwvMY OZulA6tjnwLdQe0XI1jobnbGQ3Q2v6T1QeLl52ob3rHsZQlm2D wdhTkOROigk73teh9+ez8JwaK8fRfvUR6EL3orJGa46j4dD8VB TFnYCzzb+i/oAnCsnOEAIDvQtWEqxaMWQax+pgBhwghG13G3cj tILay6GdZFL4ENvmlMh8= X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 24 September 2014 18:57:54 Ley Foon Tan wrote: > On Wed, Sep 24, 2014 at 6:40 PM, Arnd Bergmann wrote: > > On Wednesday 24 September 2014 18:18:50 Ley Foon Tan wrote: > >> On Tue, Sep 23, 2014 at 6:40 PM, Arnd Bergmann wrote: > >> > 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? > >> What is the common practice for this? > >> Do you mean merge with nios2 or other arch, eg m68k? > > > > I mean do it as part of the nios2 patches. > I am okay with this. > Do I need to get ACK for all patches in order for nios2 merge into mainline? > Thanks. > Please add my 'Acked-by: Arnd Bergmann ' to this patch once Thomas is ok with it. I think we had concluded already that it was correct when we talked about it last time, but he doesn't seem convinced yet so I want to wait for his reply. You definitely need an Ack for all patches touching code outside of arch/nios2, from the respective maintainers. For the nios2 code, having as many acks as you can helps, and I should probably take a last look so I can ack the pull request when you send it. Arnd