From: Peter Zijlstra <peterz@infradead.org>
To: Josh Don <joshdon@google.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Turner <pjt@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] sched/fair: Do not set skip buddy up the sched hierarchy
Date: Tue, 17 Dec 2019 21:42:44 +0100 [thread overview]
Message-ID: <20191217204244.GJ2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CABk29Ntp5eRFn2otK2o5Fe=uYOvKpjHgKRSw0_er45CVC025Pg@mail.gmail.com>
On Tue, Dec 17, 2019 at 11:58:28AM -0800, Josh Don wrote:
> > Ingo, Peter, what do you think ?
>
> I could add the Co-developed-by tag if that would be sufficient here.
> As a side note, I'm also looking at upstreaming our other sched
> fixes/patches, and some of these have the same issue with respect to
> the original author. How would you prefer I handle these in general?
These internal patches that you have, don't they have a SoB on from the
original author?
Ingo, Greg, how do we handle patches where the original Author has
vanished/left etc and no SoB is present?
Now, in this case we know Venki was with Google in the US, and the US
allows/has copyright assignment to employers and therefore any old SoB
from a Google person should probably be sufficient, but that argument
doesn't work in general (Germany for example doesn't allow copyright
assignment/transfer).
next prev parent reply other threads:[~2019-12-17 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 20:06 [PATCH v2] sched/fair: Do not set skip buddy up the sched hierarchy Josh Don
2019-12-06 7:57 ` Vincent Guittot
2019-12-06 22:13 ` Josh Don
2019-12-09 9:18 ` Dietmar Eggemann
2019-12-12 22:19 ` Josh Don
2019-12-18 11:36 ` Dietmar Eggemann
2019-12-18 20:02 ` Josh Don
2019-12-19 0:14 ` [PATCH v3] " Josh Don
2019-12-26 15:05 ` Vincent Guittot
2020-02-25 1:50 ` Josh Don
2019-12-12 8:05 ` [PATCH v2] " Vincent Guittot
2019-12-17 19:58 ` Josh Don
2019-12-17 20:42 ` Peter Zijlstra [this message]
2019-12-17 21:00 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2019-11-04 14:54 [PATCH] " Vincent Guittot
2019-11-06 22:14 ` [PATCH v2] " Josh Don
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=20191217204244.GJ2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox