All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Austin Christ <austinwc@codeaurora.org>,
	Tyler Baicar <tbaicar@codeaurora.org>
Subject: Re: [RFC 1/2] sched/fair: Fix load_balance() affinity redo path
Date: Fri, 12 May 2017 22:44:59 +0200	[thread overview]
Message-ID: <20170512204459.GJ4626@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <6b0aaedf-ed9a-6028-7bdc-9548f55d69af@codeaurora.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 <austinwc@codeaurora.org>
> >>Signed-off-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> >>Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> >
> >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.

  reply	other threads:[~2017-05-12 20:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 17:01 [RFC 0/2] load_balance() fixes for affinity Jeffrey Hugo
2017-05-12 17:01 ` [RFC 1/2] sched/fair: Fix load_balance() affinity redo path Jeffrey Hugo
2017-05-12 17:23   ` Peter Zijlstra
2017-05-12 17:29     ` Jeffrey Hugo
2017-05-12 20:44       ` Peter Zijlstra [this message]
2017-05-12 20:54         ` Jeffrey Hugo
2017-05-12 20:47   ` Peter Zijlstra
2017-05-12 20:57     ` Jeffrey Hugo
2017-05-15 14:56       ` Dietmar Eggemann
2017-05-18 14:31         ` Jeffrey Hugo
2017-05-12 17:01 ` [RFC 2/2] sched/fair: Remove group imbalance from calculate_imbalance() Jeffrey Hugo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170512204459.GJ4626@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=austinwc@codeaurora.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=jhugo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tbaicar@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.