netdev - Re: [PATCH] phy: add support for a reset-gpio specification

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: <573A0388.2010002@gmail.com>
Date:	Mon, 16 May 2016 10:29:44 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	David Miller <davem@...emloft.net>, u.kleine-koenig@...gutronix.de
Cc:	netdev@...r.kernel.org, devicetree@...r.kernel.org,
	kernel@...gutronix.de, afd@...com, nm@...com
Subject: Re: [PATCH] phy: add support for a reset-gpio specification

On 05/16/2016 10:23 AM, David Miller wrote:
> From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
> Date: Thu, 12 May 2016 12:00:33 +0200
> 
>> The framework only asserts (for now) that the reset gpio is not active.
>>
>> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
> 
> Applied.

Humm that was a little too quick IMHO, there are two concurrent patches
adressing the same problem right now, and Uwe's patch relies on a
specific "quirk" of specifying the Ethernet PHY's full OUI in the Device
Tree compatible string, while Sergei's approach does not require that...
AFAICT, the binding portion of the patch was also still being discussed.

I guess we will have to submit incremental patches now.
-- 
Florian