linux-kernel - Re: [PATCH v2] sched/fair: Do not set skip buddy up the sched hierarchy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABk29Ntp5eRFn2otK2o5Fe=uYOvKpjHgKRSw0_er45CVC025Pg@mail.gmail.com>
Date:   Tue, 17 Dec 2019 11:58:28 -0800
From:   Josh Don <joshdon@...gle.com>
To:     Vincent Guittot <vincent.guittot@...aro.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>
Cc:     Juri Lelli <juri.lelli@...hat.com>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Paul Turner <pjt@...gle.com>
Subject: Re: [PATCH v2] sched/fair: Do not set skip buddy up the sched hierarchy

On Thu, Dec 12, 2019 at 12:05 AM Vincent Guittot
<vincent.guittot@...aro.org> wrote:
>
> Hi Josh,
>
> On Fri, 6 Dec 2019 at 23:13, Josh Don <joshdon@...gle.com> wrote:
> >
> > Hi Vincent,
> >
> > Thanks for taking a look.
> >
> > > There is a mismatch between the author Venkatesh Pallipadi and the
> > > signoff Josh Don
> > > If Venkatesh is the original author and you have then done some
> > > modifications, your both signed-off should be there
> >
> > Venkatesh no longer works at Google, so I don't have a way to get in
> > touch with him.  Is my signed-off insufficient for this case?
>
> Maybe you can add a Co-developed-by tag to reflect your additional changes
> I guess that as long as you agree with the DCO, it's ok :
> https://www.kernel.org/doc/html/v5.4/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
>
> 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?