netdev - Re: [PATCH 0/2] MDIO bus reset GPIO 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: <eedb8398-58b7-b73e-636a-1cccc10afd98@cogentembedded.com>
Date:   Tue, 13 Jun 2017 13:28:37 +0300
From:   Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:     Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Frank Rowand <frowand.list@...il.com>, netdev@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH 0/2] MDIO bus reset GPIO cleanups

On 6/12/2017 11:55 PM, Sergei Shtylyov wrote:

> Commit 4c5e7a2c0501 ("dt-bindings: mdio: Clarify binding document")
> declared that a MDIO reset GPIO property should have only a single GPIO
> reference/specifier, however the supporting code was left intact...
> Here's a couple of the obvious cleanups to that code:

    Apparently, I forgot how to write cover letters: the patches were against 
net-next (well, at least this could be deduced from the patches themselves).

MBR, Sergei