linux-kernel - Re: [GIT PULL] pin control bulk changes for v5.4

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-=wjjP4YuM8myHkb20avZA8r=KCN3wLi2piWuPKBTH4T3vQ@mail.gmail.com>
Date:   Thu, 19 Sep 2019 14:25:29 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: [GIT PULL] pin control bulk changes for v5.4

On Thu, Sep 19, 2019 at 2:08 PM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> Alernatively you can wait for the m68k tree to come in first. Or we nudge Geert
> to send the changes ASAP. The usage of a wildly different pin
> controller on Atari hardware is only a compile testing artifact so
> we didn't drill deeper into this.

The m68k tree came in days ago, long before your pull request. It was
already merged on the first day of the merge window.

So no need to nudge Geert. We should be ok.

              Linus