netdev - Re: [PATCH net-next 0/2] net: phy: set 1Gbps as default for driver features

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] [day] [month] [year] [list]

Message-Id: <20181219.113417.365538522515438353.davem@davemloft.net>
Date:   Wed, 19 Dec 2018 11:34:17 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     hkallweit1@...il.com
Cc:     andrew@...n.ch, f.fainelli@...il.com, rjui@...adcom.com,
        sbranden@...adcom.com, bcm-kernel-feedback-list@...adcom.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: set 1Gbps as default for driver
 features

From: Heiner Kallweit <hkallweit1@...il.com>
Date: Wed, 19 Dec 2018 20:30:20 +0100

> On 19.12.2018 10:21, Andrew Lunn wrote:
>> On Tue, Dec 18, 2018 at 09:46:56PM -0800, David Miller wrote:
>>> From: Heiner Kallweit <hkallweit1@...il.com>
>>> Date: Tue, 18 Dec 2018 19:09:36 +0100
>>>
>>>> Eventually defining 1Gbps as default isn’t something we would need to roll
>>>> back later once PHYs above 1Gbps are the standard. We can deal with this in
>>>> phylib w/o affecting existing drivers. Therefore I think the proposed change
>>>> is future-proof.
>>>
>>> Andrew, what do you think given Heiner's explanation of his thinking?
>> 
>> Ah, sorry, i replied P2P to Heiner and Florian. Please give us a bit
>> of time to discuss this, we can let you know before net-next closes.
>> 
> David, we agreed to first work on clause 45 speed autodetection in phylib
> and then come up with patches including the scope of what I submitted now.
> So you can disregard the current patch series.

Ok, thanks for the update.