linux-kernel - Re: [GIT PULL]: dmaengine updates for v5.15-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:   Thu, 9 Sep 2021 11:11:02 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Vinod Koul <vkoul@...nel.org>
Cc:     dma <dmaengine@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL]: dmaengine updates for v5.15-rc1

On Tue, Sep 7, 2021 at 9:39 PM Vinod Koul <vkoul@...nel.org> wrote:
>
> Also contains, bus_remove_return_void-5.15 to resolve dependencies

That one actually has a commit message with explanations about that
branch from Greg.

There are other merges that _don't_ have any reason for them. Like
randomly merging 5.14-rc5 with no explanation.

Or the three random "merge fixes".

Please people. For the Nth time. Merges need commit messages that tell
people _why_ you merge, and what the code is that you merge. Not just
"merge tree X"

             Linus