netdev - Re: [net PATCH 1/1] net: phy: fix phy link up when limiting speed via device tree

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:	Fri, 26 Jun 2015 10:26:20 +0530
From:	Mugunthan V N <mugunthanvnm@...com>
To:	<davem@...emloft.net>
CC:	Florian Fainelli <f.fainelli@...il.com>, <netdev@...r.kernel.org>
Subject: Re: [net PATCH 1/1] net: phy: fix phy link up when limiting speed
 via device tree

On Friday 26 June 2015 08:33 AM, Florian Fainelli wrote:
> Le 06/25/15 09:51, Mugunthan V N a écrit :
>> > When limiting phy link speed using "max-speed" to 100mbps or less on a
>> > giga bit phy, phy never completes auto negotiation and phy state
>> > machine is held in PHY_AN. Fixing this issue by comparing the giga
>> > bit advertise though phydev->supported doesn't have it but phy has
>> > BMSR_ESTATEN set. So that auto negotiation is restarted as old and
>> > new advertise are different and link comes up fine.
>> > 
>> > Signed-off-by: Mugunthan V N <mugunthanvnm@...com>
> Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
> 

Dave

Forgot to tag the patch to stable@...r.kernel.org for v4.1 lts, should I
send a separate patch to Greg KH or you still hold a branch to be sent
for v4.1?

Regards
Mugunthan V N
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html