From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755737Ab3LJS24 (ORCPT ); Tue, 10 Dec 2013 13:28:56 -0500 Received: from mail-ea0-f180.google.com ([209.85.215.180]:58796 "EHLO mail-ea0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754073Ab3LJS2u (ORCPT ); Tue, 10 Dec 2013 13:28:50 -0500 Date: Tue, 10 Dec 2013 19:28:47 +0100 From: Ingo Molnar To: Davidlohr Bueso Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, dvhart@linux.intel.com, peterz@infradead.org, paulmck@linux.vnet.ibm.com, efault@gmx.de, jeffm@suse.com, torvalds@linux-foundation.org, scott.norton@hp.com, tom.vaden@hp.com, aswin@hp.com, Waiman.Long@hp.com, jason.low2@hp.com Subject: Re: [PATCH v2 4/4] futex: Avoid taking hb lock if nothing to wakeup Message-ID: <20131210182847.GB20770@gmail.com> References: <1386063927-6545-1-git-send-email-davidlohr@hp.com> <1386063927-6545-5-git-send-email-davidlohr@hp.com> <1386356686.2797.1.camel@buesod1.americas.hpqcorp.net> <20131210153629.GA1397@gmail.com> <1386692253.2731.5.camel@buesod1.americas.hpqcorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1386692253.2731.5.camel@buesod1.americas.hpqcorp.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Davidlohr Bueso wrote: > On Tue, 2013-12-10 at 16:36 +0100, Ingo Molnar wrote: > > * Davidlohr Bueso wrote: > > > > > On Fri, 2013-12-06 at 19:26 +0100, Thomas Gleixner wrote: > > > > On Tue, 3 Dec 2013, Davidlohr Bueso wrote: > > > > > Signed-off-by: Waiman Long > > > > > Signed-off-by: Jason Low > > > > > Signed-off-by: Davidlohr Bueso > > > > > > > > Who is the author of this? According to the SOB chains its Waiman, who > > > > handed it down to Jason and it finally got sumbitted by you. Is that > > > > correct? > > > > > > This was a group effort for the original patchset -- things did change > > > quite a bit for this particular patch in v2. Waiman and Jason helped > > > review and test the original atomic ops code. > > > > Then please put that into the credits (in the changelog and/or in the > > source code), and/or into copyright notices, etc. - but keep the > > SOB-chain the true route of the patch, where the primary author is the > > first in the SOB and where the person sending the patch is the last > > SOB. (the two are identical normally.) > > Ok, I wasn't aware of that primary author rule, sorry. The exact > same thing would go for patch 2 then. Is this something you want me > to correct for this particular series, or to keep in mind for the > future? Would be nice to fix it, the SOB chain is important for fine print reasons. Thanks, Ingo