linux-kernel - Re: [GIT PULL] thermal for v5.9-rc1

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]

Date:   Mon, 3 Aug 2020 20:26:01 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     Zhang Rui <rui.zhang@...el.com>,
        Amit Kucheria <amit.kucheria@...aro.org>,
        Andrzej Pietrasiewicz <andrzej.p@...labora.com>,
        Colin King <colin.king@...onical.com>,
        Shawn Guo <shawn.guo@...aro.org>,
        Lukasz Luba <Lukasz.Luba@....com>,
        Sumeet Pawnikar <sumeet.r.pawnikar@...el.com>,
        Henry Yen <henry.yen@...iatek.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM mailing list <linux-pm@...r.kernel.org>,
        Marian-Cristian Rotariu 
        <marian-cristian.rotariu.rb@...renesas.com>
Subject: Re: [GIT PULL] thermal for v5.9-rc1

On Mon, Aug 3, 2020 at 2:44 PM Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>
> ssh://git@...olite.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git
> tags/thermal-v5.9-rc1

This was all rebased just an hour before you sent it to me.

Why?

Maybe it's how you commonly work, and I just haven't noticed before,
but it's wrong for all the reasons I've stated about a million times
now.

What makes it so hard for people to understand? What makes that "you
sent me a completely untested pull request and that's not ok" so
difficult a concept to get?

And dammit, if you do it and have a good reason to do this despite
literally *decades* of me telling people not to do that, and why it's
wrong, then  you can spend the five minutes *explaining* why you do
something that is widely documented to be bad.

These commits sure as hell weren't in linux-next either.

                   Linus