linux-kernel - Re: [PATCH 00/10] sched.h modernization -v2, phase #1: "Pre-splitup cleanups"

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: <CA+55aFySho1akqNxSPaUa5b-9EMRmBmDUG+NyAqRjWysCZ8j-Q@mail.gmail.com>
Date:   Wed, 8 Feb 2017 12:23:19 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Mike Galbraith <efault@....de>,
        Oleg Nesterov <oleg@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/10] sched.h modernization -v2, phase #1: "Pre-splitup cleanups"

On Wed, Feb 8, 2017 at 10:34 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
>   phase #1: "Pre-splitup cleanups":               # 0721da143d99~1..582c7529a1bd,   10 patches
>
>   phase #2: "Prepare header dependencies":        # 9017f600c534~1..d1eb6f0b580d,   48 patches
>   phase #3: "Move definitions between headers":   # 3d01f4b6e32d~1..fd88c1773dd6,   53 patches
>   phase #4: "Remove header dependencies":         # 2d246f83c5d3~1..2205323e0ca1,   35 patches
>
>   phase #5: "Post-splitup cleanups":              # 55cf8bfb3af4~1..bcc6be9d66b2,    2 patches

So this seemed to be easier to go through, although I basically
skipped all the one-liners so who knows what conflict markers might
have been hiding there ;^)

I would personally have preferred phase 2/3 to be done in the reverse
order (by having the "move definitions" phase just add an include in
<sched.h> to still get them after the move), but it's not a huge issue
and I doubt it's worth re-doing the series over it.

I noted a couple of nits I found, but in general I think you can just
add my ack to this.

                Linus