From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758013AbdELUpI (ORCPT ); Fri, 12 May 2017 16:45:08 -0400 Received: from merlin.infradead.org ([205.233.59.134]:52822 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751574AbdELUpG (ORCPT ); Fri, 12 May 2017 16:45:06 -0400 Date: Fri, 12 May 2017 22:44:59 +0200 From: Peter Zijlstra To: Jeffrey Hugo Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Dietmar Eggemann , Austin Christ , Tyler Baicar Subject: Re: [RFC 1/2] sched/fair: Fix load_balance() affinity redo path Message-ID: <20170512204459.GJ4626@worktop.programming.kicks-ass.net> References: <1494608498-4538-1-git-send-email-jhugo@codeaurora.org> <1494608498-4538-2-git-send-email-jhugo@codeaurora.org> <20170512172334.yusgrt5qpc62wc5p@hirez.programming.kicks-ass.net> <6b0aaedf-ed9a-6028-7bdc-9548f55d69af@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6b0aaedf-ed9a-6028-7bdc-9548f55d69af@codeaurora.org> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 12, 2017 at 11:29:05AM -0600, Jeffrey Hugo wrote: > On 5/12/2017 11:23 AM, Peter Zijlstra wrote: > >On Fri, May 12, 2017 at 11:01:37AM -0600, Jeffrey Hugo wrote: > > > >>Signed-off-by: Austin Christ > >>Signed-off-by: Dietmar Eggemann > >>Signed-off-by: Jeffrey Hugo > > > >So per that Chain Austin wrote the patch, who handed it to Dietmar, who > >handed it to you. Except I don't see a From: Austin on. > > > >What gives? > > > > Austin and I did the investigations and wrote the initial version. We > discussed it with Dietmar, who suggested some significant rewrites which we > felt added to the readability of the code. The current version posted on > the list you've seen was basically written by all three of us, so I listed > the authors in alphabetical order to properly give credit to all involved. > > Is there a better way to handle patches which have authorship from multiple > people? Well, Signed-off-by is only a chain of custody thing. It says who handled the patches and that they have the right to publish and that sorts of thing. We have a document describing this. It does _NOT_ however imply any kind of authorship what so ever. Of course, the author must be the first in the custody chain, how else could the patch 'escape'. Authorship comes from the Author: header, and there's only 1 of those. Just mention the people by name in the Changelog or something.