linux-kernel - Re: [tip: locking/core] futex: Move to kernel/futex/

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: <20211009155642.GX174703@worktop.programming.kicks-ass.net>
Date:   Sat, 9 Oct 2021 17:56:42 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     André Almeida <andrealmeid@...labora.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
        linux-tip-commits@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [tip: locking/core] futex: Move to kernel/futex/

On Sat, Oct 09, 2021 at 11:23:36AM -0300, André Almeida wrote:
> Hi Peter,
> 
> Às 07:07 de 09/10/21, tip-bot2 for Peter Zijlstra escreveu:
> > The following commit has been merged into the locking/core branch of tip:
> > 
> > Commit-ID:     77e52ae35463521041906c510fe580d15663bb93
> > Gitweb:        https://git.kernel.org/tip/77e52ae35463521041906c510fe580d15663bb93
> > Author:        Peter Zijlstra <peterz@...radead.org>
> > AuthorDate:    Thu, 23 Sep 2021 14:10:50 -03:00
> > Committer:     Peter Zijlstra <peterz@...radead.org>
> > CommitterDate: Thu, 07 Oct 2021 13:51:07 +02:00
> > 
> > futex: Move to kernel/futex/
> > 
> > In preparation for splitup..
> > 
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> > Suggested-by: Thomas Gleixner <tglx@...utronix.de>
> > Signed-off-by: André Almeida <andrealmeid@...labora.com>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> > Reviewed-by: André Almeida <andrealmeid@...labora.com>
> This Signed-off-by chain seems odd, all patches to 15/22 have this, is
> it right?

Well, I wrote the patch, you reposted it and then I applied it, that
gets me there twice.

Arguably my script got the Suggested-by in the wrong place tho...