From: Jeroen Hofstee <jhofstee@victronenergy.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: "Koen Kooi" <koen@dominion.thruhere.net>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet
Date: Thu, 3 Oct 2019 08:16:46 +0000 [thread overview]
Message-ID: <436f1712-7dec-db40-d08f-1a3032af3596@victronenergy.com> (raw)
In-Reply-To: <d027ef07-807d-6a7b-2939-b67be4542469@ti.com>
Hello Grygorri,
On 10/2/19 4:48 PM, Grygorii Strashko wrote:
>
>
> On 02/10/2019 12:54, Jeroen Hofstee wrote:
>> cd28d1d6e52e: ("net: phy: at803x: Disable phy delay for RGMII mode")
>> broke
>> the ethernet networking on the beaglebone enhanced.
>
> Above commit is incorrect (by itself) and there are few more commits
> on top of
> it, so pls. update reference to commit(s)
>
> bb0ce4c1517d net: phy: at803x: stop switching phy delay config needlessly
> 6d4cd041f0af net: phy: at803x: disable delay only for RGMII mode
>
>
I don't see why that is relevant. The mention patch introduces a
backwards incompatibility for the device tree. The patches you
mention don't fix that and hence are unrelated to this patch.
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.
Regards,
Jeroen
next prev parent reply other threads:[~2019-10-03 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 9:54 [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet Jeroen Hofstee
2019-10-02 14:48 ` Grygorii Strashko
2019-10-03 8:16 ` Jeroen Hofstee [this message]
2019-10-03 9:31 ` Grygorii Strashko
2019-10-08 14:23 ` Tony Lindgren
2019-10-08 14:46 ` Jeroen Hofstee
2019-10-08 16:02 ` Jeroen Hofstee
2019-10-08 16:14 ` Tony Lindgren
2019-10-08 16:42 ` Jeroen Hofstee
2019-10-08 16:51 ` Tony Lindgren
2019-10-08 16:59 ` Jeroen Hofstee
2019-10-08 17:02 ` Tony Lindgren
2019-10-09 9:43 ` Grygorii Strashko
2019-10-09 10:09 ` Jeroen Hofstee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=436f1712-7dec-db40-d08f-1a3032af3596@victronenergy.com \
--to=jhofstee@victronenergy.com \
--cc=bcousson@baylibre.com \
--cc=grygorii.strashko@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).