[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3f824c9-92bd-1750-bdd4-dce61e618008@victronenergy.com>
Date: Tue, 8 Oct 2019 14:46:51 +0000
From: Jeroen Hofstee <jhofstee@...tronenergy.com>
To: Tony Lindgren <tony@...mide.com>,
Grygorii Strashko <grygorii.strashko@...com>
CC: "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Koen Kooi <koen@...inion.thruhere.net>,
BenoƮt Cousson <bcousson@...libre.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet
Hello Tony,
On 10/8/19 4:23 PM, Tony Lindgren wrote:
> * Grygorii Strashko <grygorii.strashko@...com> [191003 02:32]:
>> On 03/10/2019 11:16, Jeroen Hofstee wrote:
>>> Furthermore 4.19 is fine, so there is no need to include it in stable
>>> and have a note to make sure also other patches are required etc.
>> Hence all above patches went in 5.1 it would be correct to mention only
>> 6d4cd041f0af net: phy: at803x: disable delay only for RGMII mode
> Jeroen, can you please send an updated patch with the fixes
> tag changed?
Not at the moment. I am right that the mentioned commit
is the first one to break the ethernet. Grygorii is right it
seems that that commit shouldn't affect it, yet it does.
So I would like to understand how it breaks things so I can
up with a sensible commit message (or we just drop reference
to other commits so I don't have to dig through the 5.1 history,
the patch by itself is also valid).
Regards,
Jeroen
Powered by blists - more mailing lists