linux-kernel - Re: [GIT PULL] sched/urgent for 5.8-rc3

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: <CAHk-=wjqaq=otcxZfJrbRCJ31k_paP4RLOOkzLF6wwvW3aQd9A@mail.gmail.com>
Date:   Sun, 28 Jun 2020 11:40:16 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Borislav Petkov <bp@...e.de>,
        Peter Zijlstra <peterz@...radead.org>, x86-ml <x86@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] sched/urgent for 5.8-rc3

On Sun, Jun 28, 2020 at 11:15 AM Ingo Molnar <mingo@...nel.org> wrote:
>
> I based sched/urgent on a tested-working merge commit, not on a random
> interim commit - in this sense your rebase of 68f7b5cc835d was
> somewhat unnecessary.
>
> I believe avoiding random merge commits is mostly relevant in the
> merge window phase, when reliability of interim merge stages is
> arguably low and same-day rebases were a disease a couple of years
> ago.

Yes. And in general I'd prefer to not see rebases.

I took the rebased pull from Borislav already, though, so it's there now.

                  Linus