linux-kernel - Re: [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet

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: <4fa5393d-0b2c-4b8c-128a-81ab05a14a82@victronenergy.com>
Date:   Tue, 8 Oct 2019 16:42:47 +0000
From:   Jeroen Hofstee <jhofstee@...tronenergy.com>
To:     Tony Lindgren <tony@...mide.com>
CC:     Grygorii Strashko <grygorii.strashko@...com>,
        "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 6:14 PM, Tony Lindgren wrote:
> * Jeroen Hofstee <jhofstee@...tronenergy.com> [191008 16:03]:
>> 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?
>>>
>> For completeness, there is no "Fixes tag" as you mentioned.
>> The commit only refers to another commit which introduces
>> a problem.
> Well please add the fixes tag, that way this will get
> properly applied to earlier stable kernels too :)

But 4.19 is fine, this is an issue in 5.1 as in EOL...
I really don't understand why I should waste time
to figure out what happened exactly during the 5.1
release cycle...

Regards,

Jeroen